Re: [hibernate-dev] JPA 2.1 API compiled with JDK 7!?

> 1) JPA 2.1 is part of EE 7 which requires SE 7 But couldn't JPA 2.1 be used in 1.6 SE environments? I guess there'd be users doing this. Also if 1.6 is reaching its EOL there are lots of people still using it. In BV the situation is similar, it is part of the EE 7 API, but the BV spec (and thus HV) requires only 1.6. >And see the discussion that took place on this list over a year ago about O/RM and the Java 6 javac bug I don't know the details, but could this maybe circumvented by compiling with javac 1.7, but using 1.6 as target level for the generated class files? All in all I think requiring only 1.6 is very beneficial for the adoption of an API. --Gunnar 2013/2/25 Steve Ebersole <steve(a)hibernate.org <mailto:steve@hibernate.org>> Was not really a conscious decision, but keep in mind that: 1) JPA 2.1 is part of EE 7 which requires SE 7 2) Oracle Java SE 6 is past any support. And see the discussion that took place on this list over a year ago about O/RM and the Java 6 javac bug On 02/25/2013 04:07 AM, Hardy Ferentschik wrote: > Hi, > > when trying to use > > <dependency> > <groupId>org.hibernate.javax.persistence</groupId> > <artifactId>hibernate-jpa-2.1-api</artifactId> > <version>1.0.0.Draft-10</version> > </dependency> > > in Hibernate Validator I get an UnsupportedClassVersionError. > Seems the API is compiled with JDK 7, which causes problems in the HV build. > Is the use of Java 7 intentional for the JPA API? I don't think it is required, right? > > --Hardy > _______________________________________________ > hibernate-dev mailing list > hibernate-dev(a)lists.jboss.org <mailto:hibernate-dev@lists.jboss.org> > https://lists.jboss.org/mailman/listinfo/hibernate-dev _______________________________________________ hibernate-dev mailing list hibernate-dev(a)lists.jboss.org <mailto:hibernate-dev@lists.jboss.org> https://lists.jboss.org/mailman/listinfo/hibernate-dev