[MNG-4730] packaging aar declared in one module affects the following modules

• Type: Bug
• Status: Closed
• Priority: Critical
• Resolution: Duplicate
• Affects Version/s: 2.2.1
• Component/s: Reactor and Workspace
• Assignee: Benjamin Bentmann
• Reporter: Victor Bronstein
• Created: 14/Jul/10 11:44
• Updated: 17/Jul/10 12:50
• Resolved: 17/Jul/10 12:50

Description

When there is an aar module in the reactor, it causes the following modules to install (and then to deploy) their main artifact with the '.aar' extension, although they are regular JAR modules. This is a regression from 2.1.0-M1.
Attached is a project that demonstrates the problem. Inside there's also a log of mvn --debug clean install.

Issue Links

• duplicates: 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