Actually it looks like some other changes now require JDK 1.7 to be
used. Specifically some changes in either the hibernate-mapping.xsd or
in the JAXB/XJC piece that parses it. It is now trying to add an
attribute to the generated classes that is only valid in JDK 1.7
(javax.xml.bind.annotati
Wanted to make sure it was clear that as I move this out to metamodel,
building metamodel will also require JDK 1.7 to build.
Also, this does not mean we will "move to" JDK 1.7 as a base for
Hibernate 5 *necessarily*. I am open to that discussion, too, but
really it just means that right now t
Just an FYI that this code has now bee integrated into master (4.1 has
been branched off). That means that as of now, to build master you will
have to use JDK 1.7...
On 06/14/2012 10:24 AM, Steve Ebersole wrote:
> Interesting, once I got it compiled (using Java 7) I could then run the
> tests
This is the deal discussed earlier on the dev list about jdk 1.6 javac
bug. For now we will need to use jdk 1.7
On Jul 19, 2012 2:20 AM, "Strong Liu" wrote:
> our CI reported some compile error :
>
>
> [ant:javac] Compiling 206 source files to
> /mnt/hudson_workspace/workspace/hibernate-core-ma
Hi all,
I created a gist https://gist.github.com/3141182, I think it covers most big
features that mapping related.
we think it is important to get the whole picture and know where we are and how
many tasks are left
so, please update this doc and let everyone know which mapping is finished and
our CI reported some compile error :
[ant:javac] Compiling 206 source files to
/mnt/hudson_workspace/workspace/hibernate-core-master/hibernate-entitymanager/target/classes/main
[ant:javac]
/mnt/hudson_workspace/workspace/hibernate-core-master/hibernate-entitymanager/src/main/java/org/hibernate/
