[hibernate-dev] Hibernate Search 5.8.0.Beta3 released

Hello, We just released Hibernate Search 5.8.0.Beta3, with easier analyzer configuration, AWS compatibility and DI integration. You can find more information about 5.8.0.Beta3 on our blog: http://in.relation.to/2017/06/13/hibernate-search-5-8-0-Beta3/ Yoann Rodière Hibernate NoORM Team

Re: [hibernate-dev] Hibernate ORM 5.0 test failures

Byteman needs to open a socket into the JVM to inject its magic: you can't otherwise rewrite the bytecode of any class. Since various tools we use, like Byteman, Arquillian, Infinispan, WildFly, JGroups, and probably some others I'm forgetting require network ports we normally run CI build jobs

Re: [hibernate-dev] HHH-11791

On 13 June 2017 at 09:06, Gunnar Morling wrote: > 2017-06-13 7:54 GMT+02:00 Christian Beikov : >> Hi, >> >> this might work for a limited set of use cases, but what exactly are you >> expecting from that approach? Performance might be a bit

Re: [hibernate-dev] Migration path from 3.6 to 5.2

Hi, You can migrate from 3.6 to 5.2 directly. Just read all the migration guides from 3.x to 5.2 to know what has changed and what you need to take into consideration. For example, 5.x uses the enhanced identifier generators which you might want to disable if you relied on the old sequence-based

Re: [hibernate-dev] Hibernate ORM 5.0 test failures

This error: "unexpected exception opening server socket java.net.BindException: Address already in use (Bind failed)" I only got it when NVidia driver was stealing the Wildfly port, but that was never for CriteriaLockingTest. It's also curious why the Byteman agent tries to open a socket

[hibernate-dev] Hibernate ORM 5.0 test failures

I just noticed that there were a couple of failures in the CI tests: http://ci.hibernate.org/view/ORM/job/hibernate-orm-5.0-h2/lastCompletedBuild/testReport/ Both failures are from timeouts due to: java.net.BindException: Address already in use (Bind failed) It passes locally for me. This

Re: [hibernate-dev] HHH-11791

Hi, this might work for a limited set of use cases, but what exactly are you expecting from that approach? Performance might be a bit better, but that's probably negligible. Apart from that, I only see "encapsulation" or "ease of use with other languages" being your argument. Is that correct,