[ http://jira.codehaus.org/browse/MNG-468?page=comments#action_75570 ] Jason van Zyl commented on MNG-468: -----------------------------------
Milos and I will try a simple example this week but essentially it will consist of a Toolchain interface to describe everything in a toolchain, and a ToolchainAware interface so that tools can query for the ToolChain information using a ToolChainAware interface. But this interface should probably not be in Maven's core, but possibly in the plugin api. The only problem there is that it limits the toolchain awareness to plugins. Maybe that's ok. Milos and I will take a stab at resolving this during the week. > 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 > 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
