The issue is that Maven wants to use the same jvm for everything. Specifically the jvm used to lanuch maven. You can point it at different jdks for various tasks within the build, but that is static info unless you use a profile or such. We do this today for a few things. We have defined a standard property for pointing to JDK 1.6 (named jdk16_home) in Hibernate so you could make use of that like we do here: http://fisheye.jboss.org/browse/Hibernate/core/trunk/jdbc4-testing/pom.xm... or here: http://fisheye.jboss.org/browse/Hibernate/core/trunk/entitymanager/pom.xm... On Thu, 2009-10-29 at 01:30 +0100, Emmanuel Bernard wrote: > Some enforcer has been added to maven to avoid improper compilation > with the incorrect JDK. > One of the problem with that is I can't test annotations / > entitymanager (ie run tests) with JDK 6. Is there a way around that? > _______________________________________________ > hibernate-dev mailing list > hibernate-dev(a)lists.jboss.org > https://lists.jboss.org/mailman/listinfo/hibernate-dev -- Steve Ebersole <steve(a)hibernate.org&gt; Hibernate.org