[
http://jira.codehaus.org/browse/MNG-4270?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
John Casey updated MNG-4270:
----------------------------
Assignee: John Casey
Fix Version/s: 2.2.1
Need to fix this to make extensions, custom lifecycle mappings, and custom
artifact handlers more intuitive to use.
> ArtifactHandler, LifecycleMapping from plugin dependency is not used when
> plugin extensions are enabled
> -------------------------------------------------------------------------------------------------------
>
> Key: MNG-4270
> URL: http://jira.codehaus.org/browse/MNG-4270
> Project: Maven 2
> Issue Type: Bug
> Components: Plugins and Lifecycle
> Affects Versions: 2.2.0
> Reporter: John Casey
> Assignee: John Casey
> Priority: Critical
> Fix For: 2.2.1
>
>
> MNG-3506 fixed the case where two plugins with extensions enabled get in one
> another's way, and some artifact handlers are not loaded properly.
> A related issue is that artifact handlers (and lifecycle mappings) brought in
> via plugin dependencies are not used. This is because only the plugin's own
> artifact is actually scanned for extension components like ArtifactHandler or
> LifecycleMapping.
--
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
