You are viewing a plain text version of this content. The canonical link for it is here.

Posted to dev@maven.apache.org by "Brett Porter (JIRA)" <ji...@codehaus.org> on 2005/09/28 01:06:11 UTC

[jira] Closed: (MNG-831) Improve plugin API to ease configuration sharing between plugins

     [ http://jira.codehaus.org/browse/MNG-831?page=all ]
     
Brett Porter closed MNG-831:
----------------------------

      Assign To: Brett Porter  (was: John Casey)
     Resolution: Won't Fix
    Fix Version:     (was: 2.0-beta-3)

I agree with John. This is covered by properties and MNG-823 (assuming you are after it in the lifecycle and using its modified configuration). A plugin must expose what configuration to share.

> 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: dev-unsubscribe@maven.apache.org
For additional commands, e-mail: dev-help@maven.apache.org