[ http://jira.codehaus.org/browse/MAVEN-1545?page=comments#action_38728 ] Mark Proctor commented on MAVEN-1545: -------------------------------------
I forgot to mention that b) would not solve the groovy issue. b) set maven.compile.source, maven.compile.target appropriately for subprojects We tried that, didn't work, so we had to compile everything under jdk1.4 and then fork off a separate javac task to compile the jdk1.5 projects. > 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]
