[ http://jira.codehaus.org/browse/MAVEN-1545?page=comments#action_38727 ] Mark Proctor commented on MAVEN-1545: -------------------------------------
Brett, Not quite so simple. Groovy would not compiled under jdk1.5, so we had to do our own custom jdk forking within maven, not nice, as we have pure jdk1.5 modules as well. Luckily groovy has fixed this issue now and we have returned to standard multiproject builds. However for maven2.0 you might want to give this serious consideration; if Groovy or another project breaks under a future jdk version you end up with really messy build scripps - would be much easier if you can just specify JDK homes per project, like you can with eclipse. > Specify target jdk per project in multibuild > -------------------------------------------- > > Key: MAVEN-1545 > URL: http://jira.codehaus.org/browse/MAVEN-1545 > Project: maven > Type: Improvement > Versions: 1.0.2 > Reporter: Barry Kaplan > > > We have a project (Drools) in which some modules require compilation with > jdk5 and requires pre-jdk5. Both these modules cannot exists in the overall > multi-project build. > Maybe some type of property which indicates the JAVA_HOME to be used for a > project can be added. I suppose this might mean forking off a new maven when > the jdk changes from that of the top-level multi-build project. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
