[MDEP-394] unpack behaves differently in multi-module build

• Type: Bug
• Status: Closed
• Priority: Minor
• Resolution: Auto Closed
• Affects Version/s: 2.5.1, 2.6
• Component/s: unpack
• Environment: Maven 3.0.4, Mac OS X and Windows XP
• Assignee: Unassigned
• Reporter: Mike George
• Created: 07/Jan/13 09:25
• Updated: 12/Jan/16 20:12
• Resolved: 12/Jan/16 20:12

Description

During a multi-module build where one project unpacks the war from an earlier project (example attached), performing a "mvn clean test" fails with
"MojoExecutionException: Artifact has not been packaged yet. When used on reactor artifact, unpack should be executed after packaging: see MDEP-98."
at AbstractDependencyMojo.unpack(AbstractDependencyMojo.java:229)

#This will pass
mvn clean install
mvn test

1. This will fail
   mvn clean
   mvn test
2. although the custom-portal project failed, it passes when run by itself
   cd custom-portal
   mvn test

Issue Links

• relates to: MDEP-187 dependency:copy fails when invoked from m2e with workspace resolution enabled, or more generally when copying within reactor for phases earlier than package