When not being logged into JIRA, I am getting an error when opening
the "Activity" view in JIRA, e.g. at
"This gadget cannot be displayed on your dashboard. This could be
due to a licensing problem or an application error."
Anyone knows whether/how this can be fixed on our side? Or is it
something for which we need to reach out to Atlassian to get it fixed?
Karel, a user was asking about problems using the hibernate-spatial mailing
list on IRC which precipitated a discussion about how we want deal with
these things moving forward. For example, the
http://www.hibernatespatial.org/ site is still up and running and really
has no indication that the move to integrate Spatial into Hibernate proper
was completed. What do you want to have happen with that website/URL?
As for other infrastructure, what would you like to have happen? It seems
like hibernate-spatial is a more user-focused mailing list, as opposed to a
dev mailing list? If so, Hibernate does not really do user mailing lists.
We prefer the forums or StackOverflow for user questions, so there is not a
straight "migration". You can obviously keep the hibernate-spatial mailing
list running too, but we should have some idea how to help users who are
having trouble with it on the website (which website depends on what you
decide to do with http://www.hibernatespatial.org/.
Any other things we should discuss in terms of infrastructure?
Davide, what was the exact problem the user on IRC was complaining about
wrt the hibernate-spatial mailing list?
As mentioned in our last discussion, I explored adding Travis support to
The diff is here:
(yes it's short but it was a long road :))
I had to raise a bit the JGroups timeout for one test and had to fix
so that it effectively uses the configuration from the profile (this change
is not specific to Travis and should be committed anyway).
The result is here:
What I like in Travis:
- The CI configuration is code and is versioned
- Parallelization with a *lot* of resources
- The ability to build a test matrix very easily
- Complete isolation as each build is run in its own Docker container
What is less cool:
- The only way to get the logs is to ship them to AWS S3 - that said, I did
it and it's pretty straightforward as it's well integrated (I commented out
the code in the .travis.yml for now)
- It might seem less flexible as we are depending on the Travis
infrastructure (for instance, I created a ticket to ask for the support of
JDK 9: https://github.com/travis-ci/travis-ci/issues/5520) but in fact, you
can do whatever you want: see https://github.com/Blazebit/blaze-persistence
.travis.yml file for a comprehensive example
So if we move to Travis, I think the regular builds could run on Travis and
we could keep Jenkins for specific ones (deploy/release).
I'll take a look at OGM tomorrow. Travis supports out of the box most of
the NoSQL databases (https://docs.travis-ci.com/user/database-setup/) so
I'm pretty curious to see how it goes.
I got an interesting question during my talk today which I couldn't
answer right away: Is it possible to select a projection resulting
from a full-text query into a POJO/DTO?
After checking on the API of FullTextQuery again, I now realize that a
ResultTransformer could be used to instantiate POJOs based on result
Is this as good as it gets or is there any other, better way?
I have a question regarding the Elasticsearch backend: should we try to
translate the Elasticsearch exceptions to Hibernate Search exceptions (the
ones from the loggers) when possible?
Good examples of it are in
I think it might make sense for these particular examples but I wonder if
it won't be a maintenance burden in the long term.
Do you remember why the JPA User Group decided to make the ManyToOne and
the OneToOne associations EAGER by default?
In Hibernate 3.x, these associations used to be LAZY, so there must have
been a reason for taking this decision.