You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@maven.apache.org by "Mike George (JIRA)" <ji...@codehaus.org> on 2013/01/07 16:27:13 UTC
[jira] (MDEP-394) unpack behaves differently in multi-module build
Mike George created MDEP-394:
--------------------------------
Summary: unpack behaves differently in multi-module build
Key: MDEP-394
URL: https://jira.codehaus.org/browse/MDEP-394
Project: Maven 2.x Dependency Plugin
Issue Type: Bug
Components: unpack
Affects Versions: 2.6, 2.5.1
Environment: Maven 3.0.4, Mac OS X and Windows XP
Reporter: Mike George
Priority: Minor
Attachments: mvn-bug.zip
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
# This will fail
mvn clean
mvn test
# although the custom-portal project failed, it passes when run by itself
cd custom-portal
mvn test
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://jira.codehaus.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira