You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@maven.apache.org by "Mark Hobson (JIRA)" <ji...@codehaus.org> on 2005/09/03 11:25:02 UTC
[jira] Created: (MNG-831) Improve plugin API to ease configuration sharing between plugins
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
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
[jira] Closed: (MNG-831) Improve plugin API to ease configuration sharing between plugins
Posted by "Brett Porter (JIRA)" <ji...@codehaus.org>.
[ 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
[jira] Commented: (MNG-831) Improve plugin API to ease configuration sharing between plugins
Posted by "John Casey (JIRA)" <ji...@codehaus.org>.
[ http://jira.codehaus.org/browse/MNG-831?page=comments#action_47261 ]
John Casey commented on MNG-831:
--------------------------------
How much of this can be handled by POM-level properties? I'm not wild about providing a direct line of communications between any two plugins, since that could easily establish a de facto dependency between them. Mediating through the POM seems like a good idea, if it's feasible.
> 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: John Casey
> Fix For: 2.0-beta-3
>
>
> 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
[jira] Commented: (MNG-831) Improve plugin API to ease configuration sharing between plugins
Posted by "Mark Hobson (JIRA)" <ji...@codehaus.org>.
[ 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: dev-unsubscribe@maven.apache.org
For additional commands, e-mail: dev-help@maven.apache.org
[jira] Updated: (MNG-831) Improve plugin API to ease configuration sharing between plugins
Posted by "Brett Porter (JIRA)" <ji...@codehaus.org>.
[ http://jira.codehaus.org/browse/MNG-831?page=all ]
Brett Porter updated MNG-831:
-----------------------------
Fix Version: 2.0-beta-4
> 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
> Fix For: 2.0-beta-4
>
>
> 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
[jira] Updated: (MNG-831) Improve plugin API to ease configuration sharing between plugins
Posted by "Brett Porter (JIRA)" <ji...@codehaus.org>.
[ http://jira.codehaus.org/browse/MNG-831?page=all ]
Brett Porter updated MNG-831:
-----------------------------
Fix Version: (was: 2.0-beta-4)
2.1
> 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
> 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
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
For additional commands, e-mail: dev-help@maven.apache.org
[jira] Reopened: (MNG-831) Improve plugin API to ease configuration sharing between plugins
Posted by "Brett Porter (JIRA)" <ji...@codehaus.org>.
[ http://jira.codehaus.org/browse/MNG-831?page=all ]
Brett Porter reopened MNG-831:
------------------------------
I misunderstood what 823 was - it is only within the same plugin.
I have this use case for the IDEA plugin too - so I'll check whether it is necessary. Making such dependencies between plugins is one of the big pitfalls we had in m1 however, so this needs to be very carefully considered.
> 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
[jira] Updated: (MNG-831) Improve plugin API to ease configuration sharing between plugins
Posted by "Brett Porter (JIRA)" <ji...@codehaus.org>.
[ http://jira.codehaus.org/browse/MNG-831?page=all ]
Brett Porter updated MNG-831:
-----------------------------
Assign To: (was: Brett Porter)
> 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: Plugin API
> 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
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
For additional commands, e-mail: dev-help@maven.apache.org
[jira] Updated: (MNG-831) Improve plugin API to ease configuration sharing between plugins
Posted by "Brett Porter (JIRA)" <ji...@codehaus.org>.
[ http://jira.codehaus.org/browse/MNG-831?page=all ]
Brett Porter updated MNG-831:
-----------------------------
Fix Version: 2.0-beta-2
> 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
> Fix For: 2.0-beta-2
>
>
> 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