I have local database configurations for matrix testing against spatial databases. With HHH-8235 support for matrix testing has been moved into a separate project. Unfortunately, this change broke my matrix tests. I now get this error:
Execution failed for task ':hibernate-spatial:matrix_postgis'.
> No such property: project for class: org.hibernate.build.gradle.testing.database.alloc.DatabaseAllocator
Anyone an idea what I'm doing wrong?
Btw, I did update my Gradle file to include: apply plugin: 'hibernate-matrix-testing'.
Now that OSGi support is in place and we know it is being used, I am
curious whether the concept of ServiceRegistry helped or hindered in
One of the major reasons to define such a ServiceRegistry was the idea
that it would help porting Hibernate into other containers and other
runtimes, not just traditonal JSE/JEE environments. Specifically OSGi
was one of the things considered, although in a very generic sense back
then. So part of the reason I ask is that I wonder how successful we
were in that, first; and then, in areas we can get better, how?
Now is a great time to review that as we get ready to start making a
push towards 5.0 after 4.3 (JPA 2.1 support) gets stabilized...
To create the 4.3.0.Final release we're branching off from the very
stable 4.3.0.CR1 tag and applying a subset of the patches we applied
to master since them, as some are more appropriate for the next
I'll push the produced branch as "4.3" and mvn release:prepare is
going to set the next version for this branch as 4.3.1-SNAPSHOT
(however there is no expectation for an actual 4.3.1 release).
I don't think this affects any ongoing work, just don't be too
surprised if you won't see the 4.3.0.Final among the ancestors of 4.4
work in your git logs.
With the CI slowly getting in place. Would there be a way to test a
branch of mine without having to push it as a pull-request?
When I push a branch on emmanuelbernard/hibernate-search.git without
creating a PR, it would still be nice to be able to have it run.
I know we had a debate but I can't seem to find any detail in the
documentation about how facet selection influences the facet counts.
In my demo, the facet count is applied after the selection. ie if I do a
query that returns '< $100' = 20 and '> $100' = 45, once I select '<
$100', the count displayed on '> $100' = 0 which is very weird from a
use point of view.
That seems to be the expected behavior according to
https://hibernate.atlassian.net/browse/HSEARCH-713 but my first reaction
was that it was a bug.
Should we clarify that in the documentation? And implement the more