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

Posted to issues@maven.apache.org by "Jason van Zyl (JIRA)" <ji...@codehaus.org> on 2009/05/16 16:37:45 UTC

[jira] Closed: (MNG-3631) Introduce new MavenEmbedder.getPluginConfiguration method

     [ 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