Re: [hibernate-dev] Hibernate ORM and Java 8 usage

2016-01-11 Thread Vlad Mihalcea
I used Java 8 syntax in the User Guide tests as I remembered that tests can use it, but I also agree that this is a rather strange move. Since we need to support Java 1.6, maybe it's a better idea to use the latest JDK just in the modules where we have no other choice. For testing, I think that 1.6

Re: [hibernate-dev] Hibernate ORM and Java 8 usage

2016-01-11 Thread Steve Ebersole
The former. People commit things that already assume the move to Java 8 locally to build (and test). But at the moment we have not formalized that, and so that causes problems when we import into an IDE - the imported IDE project is built for 1.6 compliance and so everything we try in the IDE fai

Re: [hibernate-dev] Hibernate ORM and Java 8 usage

2016-01-11 Thread Gunnar Morling
Hey, > or we move to Java 8 and rely on > AnimalSniffer to make sure we are still compatible. WDYM by "move to Java8" exactly? Requiring it at Hibernate's build time, or also at runtime in user apps? 2016-01-11 19:49 GMT+01:00 Steve Ebersole : > The use of Java 8 features in Hibernate ORM is st

[hibernate-dev] Hibernate ORM and Java 8 usage

2016-01-11 Thread Steve Ebersole
The use of Java 8 features in Hibernate ORM is starting to expand. Luckily it is still constrained to just tests. However these usages make development in an IDE more and more difficult. Previously this was isolated to hibernate-infinispan. Now[1] this has crept into hibernate-entitymanager. We

Re: [hibernate-dev] 5.1 tentative release date

2016-01-11 Thread Sanne Grinovero
Hi Alex! I'm not expecting you to be able to work much on that 107 based cache.. if you can that's great of course, but realistically if you could just make it good enough for a PR then I think we should be able to help finish that. The "extension points" we discussed can certainly wait to be imple

Re: [hibernate-dev] 5.1 tentative release date

2016-01-11 Thread Alex Snaps
Right, there was no plan to provide something for Ehcache3 quite yet. That being said, I wonder whether we ever will. I have a 107 compliant H2LC implementation. I also went over it with Sanne during Javaone and we think it can be made into something suiting for bunch of providers. Now, small cavea

Re: [hibernate-dev] 5.1 tentative release date

2016-01-11 Thread Steve Ebersole
On Fri, Jan 8, 2016 at 9:00 PM Scott Marlow wrote: > Should we also look at changing Hibernate to not require Javassist > classes be on the deployment classpath? I just don't see how that is ever going to be realistically possible. If you have specific suggestions, we are all ears ;) _

Re: [hibernate-dev] 5.1 tentative release date

2016-01-11 Thread Steve Ebersole
Petar, Alex Snaps (in CC) has been doing some work to update the version of Ehcache used in Hibernate ORM. Alex, any updates? As I understood it though Ehcache 3.x was not part of that effort, but Alex can of course say for sure. On Sat, Jan 9, 2016 at 3:25 AM Petar Tahchiev wrote: > Hello a

Re: [hibernate-dev] 5.1 tentative release date

2016-01-11 Thread Scott Marlow
Do we have any feedback from the Infinispan team, as to what version of Infinispan should be included in ORM 5.1? From the WildFly perspective, we are currently using Infinispan 8.1.0.Final in WildFly 10 but I have no idea which version will be used in WildFly 11.0. On 01/08/2016 10:08 AM, Ste

Re: [hibernate-dev] Not letting Jenkins auto-close PRs upon build failures

2016-01-11 Thread Sanne Grinovero
This is finally fixed. Had to upgrade the plugin too, let's keep an eye on it for other possible regressions. On 8 Jan 2016 14:56, "Gunnar Morling" wrote: > 2016-01-08 14:39 GMT+01:00 Sanne Grinovero : > > Do you have an example of such a PR being closed? > > Yes, https://github.com/hibernate/hib