[ http://jira.codehaus.org/browse/MNG-4523?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=207019#action_207019
]
Peter Lynch commented on MNG-4523:
----------------------------------
Related discussion going on http://old.nabble.com/-DISCUSS--Effect-of-direct-plugin-invocation-on-model-td27087903.html
> [Regression] Plugin model inheritance different when a mojo goal is explicitly called
from cmd line
> -----------------------------------------------------------------------------------------------------
>
> Key: MNG-4523
> URL: http://jira.codehaus.org/browse/MNG-4523
> Project: Maven 2 & 3
> 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 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
|