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
fails.
On Mon, Jan 11, 2016 at 3:33 PM Gunnar Morling <gunnar(a)hibernate.org> wrote:
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 <steve(a)hibernate.org>:
> 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 need to have a plan here. Either
> we stop using Java 8 anywhere, or we move to Java 8 and rely on
> AnimalSniffer to make sure we are still compatible.
>
> Votes? Other options?
>
> [1]
>
https://github.com/hibernate/hibernate-orm/commit/c2ece0108ed52d5e3a227ed...
> _______________________________________________
> hibernate-dev mailing list
> hibernate-dev(a)lists.jboss.org
>
https://lists.jboss.org/mailman/listinfo/hibernate-dev