Master is 5.2. There was a previous discussion on this list detailing the
5.2 changes. Where possible we did not change APIs (though there were a
few cases where that was needed to avoid clashes with JPA method names).
We did change lots of SPIs though.
If you are willing to commit to getting th
Hey Steve,
That's a tough question.
For tomorrow I don't see how ... Technically the code is out there. But it
lacks documentation which is needed: how to select a specific provider and
specify a URI which can be used as config source. That still needs to be
added.
In one week, more likely. I am
https://hibernate.atlassian.net/browse/HHH-10770
On Tue, May 24, 2016 at 3:51 PM Steve Ebersole wrote:
> Hi Louis,
>
> In my opinion,
>
>- Yes, of course :)
>- The plan is to release 5.2 tomorrow. So either this would have to
>be done tomorrow or the release date pushed back in orde
Hi Louis,
In my opinion,
- Yes, of course :)
- The plan is to release 5.2 tomorrow. So either this would have to be
done tomorrow or the release date pushed back in order for this to be part
of 5.2. We could push 5.2 another week, but would the work for this be
done in a week?
Hello,
I have a couple questions:
* Should there be an issue created to track this work?
* On which branch should this work based if we target a release with 5.2?
In parallel, I have been reading the pointers Vlad gave and I intend to
verify the current code actually works in all these cases :-)
Hi All,
I filed https://hibernate.atlassian.net/browse/HHH-10707 toward the end of last
month, and was wondering what the best way was to go about getting this moved
forward. My analysis indicates that for users configured such that they trip
this bug (those sharing a single cache region acros
Hello all,
we released Hibernate Search 5.6.0.Beta1, with many more improvements
for our Elasticsearch integration.
More details on our blog:
- http://in.relation.to/2016/05/24/ElasticsearchintegrationReachesBeta1/
Regards,
Sanne
___
hibernate-dev mai
