[ http://jira.codehaus.org/browse/MNG-831?page=comments#action_47334 ]
Mark Hobson commented on MNG-831: --------------------------------- As long as the properties that a plugin sets are well documented and namespaced. My only concern is property name clashes with user pom properties - would it be safer using the plugin context from MNG-823 across multiple plugins? That way the properties are isolated from the user and only accessible by the plugin developers. > Improve plugin API to ease configuration sharing between plugins > ---------------------------------------------------------------- > > Key: MNG-831 > URL: http://jira.codehaus.org/browse/MNG-831 > Project: Maven 2 > Type: Improvement > Components: maven-plugin-api > Versions: 2.0-beta-1 > Reporter: Mark Hobson > Assignee: Brett Porter > > > 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 --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
