[ http://jira.codehaus.org/browse/MNG-710?page=comments#action_44135 ]
Rod Coffin commented on MNG-710: -------------------------------- The problem is that users of this plugin can specify any arbitrary java compiler. So the compiler type (IBM, Sun, etc.) and version could all vary. I don't know if it would be wise to attempt to anticipate which arguments might be valid and which might not. That is why I separated out a core set of common arguments which are just the minimum set of arguments (output directory, classpath, and source path). Is your concern passing the args from the compile method to the compileOutOfProcess and compileInProcess methods? If so, how about having each compilation method create its own arguments using the addXXXArguments method? Working directory was added to allow users to define which directory to run the compiler from. In hindsight it could probably be removed. > 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 > Attachments: maven-compiler-plugin.diff.txt, plexus-compiler-api.diff.txt, > plexus-compiler-javac.diff.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]
