You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@maven.apache.org by "Igor Fedorenko (JIRA)" <ji...@codehaus.org> on 2008/06/25 21:15:27 UTC
[jira] Created: (MNG-3631) Introduce new
MavenEmbedder.getPluginConfiguration method
Introduce new MavenEmbedder.getPluginConfiguration method
---------------------------------------------------------
Key: MNG-3631
URL: http://jira.codehaus.org/browse/MNG-3631
Project: Maven 2
Issue Type: Improvement
Affects Versions: 2.1
Reporter: Igor Fedorenko
There are five sources for maven plugin configuration -- build/plugins, parent build/plugins, build/pluginManagement, parent build/pluginManagement and plugin default configuration. Currently, MavenEmbedder.readProjectWithDependencies never considers default plugin configuration. Also, lifecycle-included plugins and configuration are not considered during readProjectWithDependencies (see MNGECLIPSE-627).
It would be nice to have new method MavenEmbedder.getPluginConfiguration( MavenProject project, String pluginKey ): PlexusConfiguration (or similar) which would calculate and return fully inherited/interpolated plugin configuration.
--
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
[jira] Commented: (MNG-3631) Introduce new
MavenEmbedder.getPluginConfiguration method
Posted by "Shane Isbell (JIRA)" <ji...@codehaus.org>.
[ http://jira.codehaus.org/browse/MNG-3631?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=165480#action_165480 ]
Shane Isbell commented on MNG-3631:
-----------------------------------
I have this checked into trunk. Once verified that it works as expected, I'll close out this issue.
> Introduce new MavenEmbedder.getPluginConfiguration method
> ---------------------------------------------------------
>
> Key: MNG-3631
> URL: http://jira.codehaus.org/browse/MNG-3631
> Project: Maven 2
> Issue Type: Improvement
> Affects Versions: 3.0
> Reporter: Igor Fedorenko
> Assignee: Shane Isbell
> Fix For: 3.0-alpha-3
>
>
> There are five sources for maven plugin configuration -- build/plugins, parent build/plugins, build/pluginManagement, parent build/pluginManagement and plugin default configuration. Currently, MavenEmbedder.readProjectWithDependencies never considers default plugin configuration. Also, lifecycle-included plugins and configuration are not considered during readProjectWithDependencies (see MNGECLIPSE-627).
> It would be nice to have new method MavenEmbedder.getPluginConfiguration( MavenProject project, String pluginKey ): PlexusConfiguration (or similar) which would calculate and return fully inherited/interpolated plugin configuration.
--
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
[jira] Closed: (MNG-3631) Introduce new
MavenEmbedder.getPluginConfiguration method
Posted by "Jason van Zyl (JIRA)" <ji...@codehaus.org>.
[ http://jira.codehaus.org/browse/MNG-3631?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Jason van Zyl closed MNG-3631.
------------------------------
Resolution: Fixed
This has been reworked and the POM is now fully interpolated so requesting a configuration from a Plugin object contains everything required.
> Introduce new MavenEmbedder.getPluginConfiguration method
> ---------------------------------------------------------
>
> Key: MNG-3631
> URL: http://jira.codehaus.org/browse/MNG-3631
> Project: Maven 2
> Issue Type: Improvement
> Affects Versions: 3.0
> Reporter: Igor Fedorenko
> Assignee: Shane Isbell
> Fix For: 3.0-alpha-3
>
>
> There are five sources for maven plugin configuration -- build/plugins, parent build/plugins, build/pluginManagement, parent build/pluginManagement and plugin default configuration. Currently, MavenEmbedder.readProjectWithDependencies never considers default plugin configuration. Also, lifecycle-included plugins and configuration are not considered during readProjectWithDependencies (see MNGECLIPSE-627).
> It would be nice to have new method MavenEmbedder.getPluginConfiguration( MavenProject project, String pluginKey ): PlexusConfiguration (or similar) which would calculate and return fully inherited/interpolated plugin configuration.
--
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
[jira] Updated: (MNG-3631) Introduce new
MavenEmbedder.getPluginConfiguration method
Posted by "Brett Porter (JIRA)" <ji...@codehaus.org>.
[ http://jira.codehaus.org/browse/MNG-3631?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Brett Porter updated MNG-3631:
------------------------------
Fix Version/s: 2.1
> Introduce new MavenEmbedder.getPluginConfiguration method
> ---------------------------------------------------------
>
> Key: MNG-3631
> URL: http://jira.codehaus.org/browse/MNG-3631
> Project: Maven 2
> Issue Type: Improvement
> Affects Versions: 2.1
> Reporter: Igor Fedorenko
> Fix For: 2.1
>
>
> There are five sources for maven plugin configuration -- build/plugins, parent build/plugins, build/pluginManagement, parent build/pluginManagement and plugin default configuration. Currently, MavenEmbedder.readProjectWithDependencies never considers default plugin configuration. Also, lifecycle-included plugins and configuration are not considered during readProjectWithDependencies (see MNGECLIPSE-627).
> It would be nice to have new method MavenEmbedder.getPluginConfiguration( MavenProject project, String pluginKey ): PlexusConfiguration (or similar) which would calculate and return fully inherited/interpolated plugin configuration.
--
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
[jira] Updated: (MNG-3631) Introduce new
MavenEmbedder.getPluginConfiguration method
Posted by "Shane Isbell (JIRA)" <ji...@codehaus.org>.
[ http://jira.codehaus.org/browse/MNG-3631?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Shane Isbell updated MNG-3631:
------------------------------
Fix Version/s: (was: 3.x)
3.0-alpha-3
> Introduce new MavenEmbedder.getPluginConfiguration method
> ---------------------------------------------------------
>
> Key: MNG-3631
> URL: http://jira.codehaus.org/browse/MNG-3631
> Project: Maven 2
> Issue Type: Improvement
> Affects Versions: 3.0
> Reporter: Igor Fedorenko
> Assignee: Shane Isbell
> Fix For: 3.0-alpha-3
>
>
> There are five sources for maven plugin configuration -- build/plugins, parent build/plugins, build/pluginManagement, parent build/pluginManagement and plugin default configuration. Currently, MavenEmbedder.readProjectWithDependencies never considers default plugin configuration. Also, lifecycle-included plugins and configuration are not considered during readProjectWithDependencies (see MNGECLIPSE-627).
> It would be nice to have new method MavenEmbedder.getPluginConfiguration( MavenProject project, String pluginKey ): PlexusConfiguration (or similar) which would calculate and return fully inherited/interpolated plugin configuration.
--
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