[
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
