[jira] [Closed] (MDEP-394) unpack behaves differently in multi-module build

["Michael Osipov (JIRA)" <ji...@apache.org>]

     [ https://issues.apache.org/jira/browse/MDEP-394?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Michael Osipov closed MDEP-394.
-------------------------------
    Resolution: Auto Closed

This issue has been auto closed because it has been inactive for a long period of time. If you think this issue still persists, retest your problem with the most recent version of Maven and the affected component, reopen and post your results.

> unpack behaves differently in multi-module build
> ------------------------------------------------
>
>                 Key: MDEP-394
>                 URL: https://issues.apache.org/jira/browse/MDEP-394
>             Project: Maven Dependency Plugin
>          Issue Type: Bug
>          Components: unpack
>    Affects Versions: 2.5.1, 2.6
>         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 was sent by Atlassian JIRA
(v6.3.4#6332)