You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@maven.apache.org by "Brett Porter (JIRA)" <ji...@codehaus.org> on 2007/09/05 09:21:11 UTC
[jira] Updated: (MNG-831) [toolchain] Improve plugin API to ease
configuration sharing between plugins
[ http://jira.codehaus.org/browse/MNG-831?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Brett Porter updated MNG-831:
-----------------------------
Summary: [toolchain] Improve plugin API to ease configuration sharing between plugins (was: Improve plugin API to ease configuration sharing between plugins)
I think toolchain + build context eliminates the need for this
> [toolchain] Improve plugin API to ease configuration sharing between plugins
> ----------------------------------------------------------------------------
>
> Key: MNG-831
> URL: http://jira.codehaus.org/browse/MNG-831
> Project: Maven 2
> Issue Type: Improvement
> Components: Plugin API
> Affects Versions: 2.0-beta-1
> Reporter: Mark Hobson
> Fix For: 2.1
>
>
> Plugins that need to introspect other plugin's configuration have to go via the Xpp3Dom configuration object. It'd be nice if this was easier for plugin authors. Some current use-cases are:
> * Eclipse plugin requires compiler plugin's configuration to write .settings file
> * Tomcat plugin requires war plugin's configuration to locate final war file and exploded state
--
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