You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@maven.apache.org by "Eric Pabst (JIRA)" <ji...@codehaus.org> on 2013/04/22 15:32:53 UTC

[jira] (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

    [ https://jira.codehaus.org/browse/MDEP-187?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=324053#comment-324053 ] 

Eric Pabst commented on MDEP-187:
---------------------------------

This problem happens when running phases before package (e.g. "compile", "test-compile", "process-classes").  A simple work-around that is often possible is to move the dependency:copy to a later phase such as prepare-package, which would rarely if ever be invoked directly, but instead be part of running "mvn package" (or a later phase).
                
> dependency:copy fails when invoked from m2e with workspace resolution enabled, or more generally when copying within reactor for phases earlier than package
> ------------------------------------------------------------------------------------------------------------------------------------------------------------
>
>                 Key: MDEP-187
>                 URL: https://jira.codehaus.org/browse/MDEP-187
>             Project: Maven 2.x Dependency Plugin
>          Issue Type: Bug
>          Components: copy, copy-dependencies
>    Affects Versions: 2.1
>            Reporter: Igor Fedorenko
>         Attachments: MDEP-187b.diff, MDEP-187c.diff, MDEP-187.diff
>
>
> m2e resolves workspace artifacts to their output folders but dependency:copy expects all artifacts to be files. I will provide trivial patch shortly.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira