[ http://jira.codehaus.org/browse/MNG-710?page=comments#action_44181 ]
Rod Coffin commented on MNG-710: -------------------------------- I think checking the fork flag would work if you specify source and target in your plugin configuration. Basically if forking those flags wouldn't be set by default but could be specified explicitly. How does this compare in your opinion to passing a compiler version parameter? I like putting the onus on the developer using an out of process compiler to specify the appropriate arguments. That way we don't have to anticipate all these cases in the plexus compiler. I definitely agree about making all this testable. It is a little challenging to unit test invoking a compiler. But certainly we can define and test the argument reqs. > Add ability to fork the maven-compiler-plugin > --------------------------------------------- > > Key: MNG-710 > URL: http://jira.codehaus.org/browse/MNG-710 > Project: Maven 2 > Type: Improvement > Components: maven-plugins > Reporter: Rod Coffin > Assignee: Trygve Laugstol > Fix For: 2.0-beta-1 > Attachments: maven-compiler-plugin.diff.txt, plexus-compiler-api.diff.txt, > plexus-compiler-javac.diff.txt, plexus-compiler-javac.diff2.txt > > > Add the ability to fork the maven-compiler-plugin. This would allow projects > to be compiled with a JDK other than the one used to run Maven from. -- 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]
