FYI, coincidentally I was looking at Java 7 adoption for JBoss Tools users and currently that is at ~24% out ouf ~730.000 starts the last month.
Plus Java 7 is not very stable for anything that has do with graphical rendering on either OSX and Linux OpenJDK - so it would currently be a shame if Hibernate would require it yet IMO. /max On 16 Nov 2012, at 15:40, Steve Ebersole <st...@hibernate.org> wrote: > Because we never agreed to move to 1.7. And I don't think it makes > sense. Java 6 is not even EOL yet (close, yes). > > The only 1.7 source requirement as I understand it is that jaxb > "required" thing that you added. > > We do currently need *javac* from 1.7 to compile master (and metamodel > since we are merging master into it) but that is due to a bug in the 1.6 > javac (see earlier email to the dev list). But there is actually > nothing there that is not 1.6 compatible in either source nor bytecode. > > On 11/16/2012 01:23 AM, Strong Liu wrote: >> seeing this all the times: >> >> warning: [options] bootstrap class path not set in conjunction with -source >> 1.6 >> >> >> since now we need JDK 7 to compile master/metamodel, is there any reason >> that we still set the source level to 1.6? >> >> >> ------------------------- >> Best Regards, >> >> Strong Liu <stliu at hibernate.org> >> http://about.me/stliu/bio >> >> _______________________________________________ >> hibernate-dev mailing list >> hibernate-dev@lists.jboss.org >> https://lists.jboss.org/mailman/listinfo/hibernate-dev > > > -- > st...@hibernate.org > http://hibernate.org > > _______________________________________________ > hibernate-dev mailing list > hibernate-dev@lists.jboss.org > https://lists.jboss.org/mailman/listinfo/hibernate-dev _______________________________________________ hibernate-dev mailing list hibernate-dev@lists.jboss.org https://lists.jboss.org/mailman/listinfo/hibernate-dev