Maven build fails on some systems when using jdk 6 and maven 2.x
Description
When building Core using Java 6 artifacts are renamed during install from *.jar to *.jdocbook-style (at list in the core sub-module). This of course screws up the local repo. Here is the build log of a mvn install in the core module:
The maven version is: Apache Maven 2.2.1 (r801777; 2009-08-06 21:16:01+0200) Strong was able to reproduce the problem on his Fedora box, but on this Mac it works.
Activity
Brett MeyerMarch 7, 2014 at 5:30 PM
Bulk closing rejected tickets in "resolved" state.
Steve EbersoleMay 5, 2011 at 3:24 PM
Aside from build time checks in the scripts, not sure what it is we can do here. Maven2 simply has a bug. You will not be able to use Java 6 and Maven 2 to build Hibernate.
Steve EbersoleApril 6, 2011 at 9:53 PM
Um, what exactly is it y'all think is the solution here.
Strong LiuMarch 30, 2011 at 1:25 PM
maybe it is a feature of maven? it tries to tell you do not use jdk6 to build core 3.6
Former userMarch 9, 2011 at 1:00 AM
I'm not seeing this issue using jdk 1.5 on rhel. Since I will be building the 3.6.2 release, this will not affect that release. I'm moving to 3.6.3 as a reminder to check this again in the environment used for that release.
When building Core using Java 6 artifacts are renamed during install from *.jar to *.jdocbook-style (at list in the core sub-module). This of course screws up the local repo. Here is the build log of a mvn install in the core module:
The maven version is: Apache Maven 2.2.1 (r801777; 2009-08-06 21:16:01+0200)
Strong was able to reproduce the problem on his Fedora box, but on this Mac it works.