[ http://jira.codehaus.org/browse/MNG-468?page=comments#action_78283 ] John Casey commented on MNG-468: --------------------------------
One way to avoid locking this into the plugin api would be to make the Mojo interface extent ToolchainAware, then AbstractMojo could provide a default (empty) implementation of the methods in ToolchainAware. This allows the plugin API to bring in ToolchainAware from a dependency, which could also be used elsewhere in Maven. > ability to consistently apply a toolchain across plugins > -------------------------------------------------------- > > Key: MNG-468 > URL: http://jira.codehaus.org/browse/MNG-468 > Project: Maven 2 > Issue Type: New Feature > Reporter: Brett Porter > Assigned To: Jason van Zyl > Priority: Minor > Fix For: 2.1 > > Attachments: build.properties, project.properties > > > for things like the JDK, it may be desirable to compile, jar etc. across the > board with a particular version of the toolchain, other than the one > currently executing. It would be good to be able to configure this location > in the settings.xml and have the plugins use it, forking the compiler, using > a particular runtime, and generating an appropriate manifest. > This is likely to be relevant to other languages too. -- 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
