I could not announce on twitter @hibernate_dev or on Google+. Could someone
please add those announcements please?
Thanks,
Gail
___
hibernate-dev mailing list
hibernate-dev@lists.jboss.org
https://lists.jboss.org/mailman/listinfo/hibernate-dev
http://in.relation.to/2015/12/16/hibernate-orm-506-final-release/
___
hibernate-dev mailing list
hibernate-dev@lists.jboss.org
https://lists.jboss.org/mailman/listinfo/hibernate-dev
Please do not push commits to 5.0 branch until after 5.0.6 is released.
Thanks,
Gail
___
hibernate-dev mailing list
hibernate-dev@lists.jboss.org
https://lists.jboss.org/mailman/listinfo/hibernate-dev
Hi,
Is there an actual need for 8.1 at this point (so does it provide
features we really need in OGM?) or is this more a general/theoretical
proposal?
I like the idea in general, but we must carefully think through all
the implications, such as what module slot to depend on in the OGM
dialect and
Hi Sanne,
I'm not that thrilled about it. We have at least 2 blocking bugs to fix in
5.5.2 and if there is a regression in Lucene 5.4 for one reason or another,
we won't be able to upgrade to 5.5.2.
Would prefer it to go in a 5.6 release.
--
Guillaume
On Wed, Dec 16, 2015 at 2:22 PM, Sanne Gri
I'd prefer us to do this in a minor version, i.e. 5.6.
As we expose Query to users, the removal of these methods may cause
compilation errors on their side. Also the deprecation of Filter may
cause many deprecations in client code.
Both seem not appropriate for a micro release to me.
I don't thi
Well keeping in mind that IMO this should be a separate optimizer (I know I
won't be the only one to be leery of ThreadLocals here), users should be
able to specify this one explicitly at the generator-definition site.
Of course not all use cases allow explicitly specifying this, which is sort
of
On 12/16/2015 09:07 AM, Scott Marlow wrote:
> Any arguments against merging the
> https://github.com/scottmarlow/hibernate-orm/commits/pooledOptimizer_5.x
> change to master + 5.x?
>
> I will create a jira for this change.
>
> Any suggestions for how to specify in persistence.xml, that the
> Pool
Hi Sanne,
> Although, it doesn't affect any of our code not examples so a release
> note might be acceptable.
>
> There are several other interesting performance improvements.
> So I'm tempted to upgrade to this version in the next maintenance
> (micro) release of Hibernate Search 5.5.
>
> What
On 12/16/2015 09:07 AM, Scott Marlow wrote:
> Any arguments against merging the
> https://github.com/scottmarlow/hibernate-orm/commits/pooledOptimizer_5.x
> change to master + 5.x?
>
> I will create a jira for this change.
HHH-10381
>
> Any suggestions for how to specify in persistence.xml, tha
Any arguments against merging the
https://github.com/scottmarlow/hibernate-orm/commits/pooledOptimizer_5.x
change to master + 5.x?
I will create a jira for this change.
Any suggestions for how to specify in persistence.xml, that the
PooledThreadLocalLoOptimizer should be used? We already have
Hello all,
Apache Lucene 5.4.0 is released as stable, and while it includes
several benefits - not least a performance fix from myself which I'd
be keen to take advantage of - there are no significant changes
visible to end users, expect I think this one is worth a warning:
LUCENE-6590: Query.se
Hello all,
we generally have been trying to target the versions of Infinispan
provided by the WildFly version we're targeting for compatibility with
a specific OGM release cycle.
I would like to change that, and for example now switch to the latest
Infinispan 8.1.0.Final (rather than the one in W
13 matches
Mail list logo
