Maven 2 & 3

ArtifactHandler, LifecycleMapping from plugin dependency is not used when plugin extensions are enabled

Details

  • Type: Bug Bug
  • Status: Closed Closed
  • Priority: Critical 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 :
    0

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

is related to

Bug - A problem which impairs or prevents the functions of the product. MNG-3506 Custom ArtifactHandler not resolved for project when an additional plugin with extensions is defined in parent pom

  • Blocker - Blocks development and/or testing work, production could not run
  • Closed - The issue is considered finished, the resolution is correct. Issues which are not closed can be reopened.

Activity

Hide
Permalink
John Casey added a comment -

Need to fix this to make extensions, custom lifecycle mappings, and custom artifact handlers more intuitive to use.

Show
John Casey added a comment - Need to fix this to make extensions, custom lifecycle mappings, and custom artifact handlers more intuitive to use.

People

  • Assignee:
    John Casey
    Reporter:
    John Casey
Vote (0)
Watch (0)

Dates

  • Created:
    Updated:
    Resolved: