Details
-
Type:
Bug
-
Status:
Closed
-
Priority:
Critical
-
Resolution: Fixed
-
Affects Version/s: 2.2.0
-
Fix Version/s: 2.2.1
-
Component/s: Plugins and Lifecycle
-
Labels:None
-
Complexity:Intermediate
-
Number of attachments :
Description
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.
Issue Links
| This issue is related to: | ||||
| MNG-3506 | Custom ArtifactHandler not resolved for project when an additional plugin with extensions is defined in parent pom |
|
|
|
Need to fix this to make extensions, custom lifecycle mappings, and custom artifact handlers more intuitive to use.