[
https://jira.codehaus.org/browse/MNG-4523?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Paul Benedict updated MNG-4523:
-------------------------------
Fix Version/s: (was: Issues to be reviewed for 3.x)
> [Regression] Plugin model inheritance different when a mojo goal is
> explicitly called from cmd line
> -----------------------------------------------------------------------------------------------------
>
> Key: MNG-4523
> URL: https://jira.codehaus.org/browse/MNG-4523
> Project: Maven
> Issue Type: Bug
> Affects Versions: 3.0-alpha-6
> Reporter: Peter Lynch
> Attachments: mng-4523-IT.zip
>
>
> Parent pom has a plugin configured inside pluginManagement, nothing in build
> ->plugins -> plugin
> When that plugin's mojo is called explicitly from the cmd line, the Project
> model for the parent pom is not the same in Maven 3 as in previous Maven
> versions. Specifically looking for the plugin using code such as
> {code:java}
> Build build = project.getBuild();
> Plugin plugin = (Plugin)
> build.getPluginsAsMap().get("org.apache.maven.its.test:plugin");
> // plugin is null even though defined via plugin mgt
> {code}
> demonstrates that the list of plugins in the model is different between Maven
> 2.2.1 and Maven 3.x
> Maven 2.2.1, the plugin is found using the above call.
--
This message was sent by Atlassian JIRA
(v6.1.6#6162)
