[MNG-4654] Maven erroneously selects artifact handler contributed by extension plugin for use with project main artifact based on the handler's packaging rather than type

• Type: Bug
• Status: Closed
• Priority: Major
• Resolution: Fixed
• Affects Version/s: 2.2.1
• Fix Version/s: 3.0-alpha-3
• Component/s: Artifacts and Repositories
• Assignee: Benjamin Bentmann
• Reporter: Benjamin Bentmann
• Created: 01/May/10 12:40
• Updated: 17/Jul/10 12:00
• Resolved: 01/May/10 12:43

Description

This is mostly to track the result of Compilation problem with Maven 3.0-beta-1 reported by Henrique Prange. In essence, given an artifact handler with

<configuration>
  <type>woframework</type>
  <extension>jar</extension>
  <packaging>jar</packaging>
</configuration>

and a project with <packaging>woframework</packaging> using an extension plugin contributing the above artifact handler, Maven ignores the artifact handler because it tries to match project.packaging with artifactHandler.packaging. As a result, the project's main artifacts ends up being installed/deployed with the file extension "woframework" instead of "jar".

Issue Links

• is duplicated by: MNG-4730 packaging aar declared in one module affects the following modules
• is related to: MNG-729 Ability to additional ArtifactHandlers using external components.xml