[
https://jira.codehaus.org/browse/MDEP-187?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=356251#comment-356251
]
Hannes Kogler commented on MDEP-187:
------------------------------------
Perhaps the logging gives some important hints for fixing this bad issue...
[*m2e plugin version*: 1.6.0.20140823-1318; using standalone Maven version
3.2.3]
[*eclipse version*: Luna Service Release 1 (4.4.1); Build id 20140925-1800]
if the workspace resolution is deactivated, the copying works and the message
in the Maven console says:
{color:blue}11/17/14, 12:57:32 PM GMT+1: [INFO] *Copying*
some.project-XX.XX.XX.jar to
C:\workspaces\some.other\target\some.project.jar{color}
if the workspace resolution is ACTIVE, m2e starts any other process on the
maven-dependency-plugin and fails copying with the message in the Maven console:
{color:blue}11/17/14, 1:15:02 PM GMT+1: [INFO] *Copying classes* to
C:\workspaces\some.other\target\some.project.jar{color}
*After all when failing he tries to copy only the classes of the jar file??!! *
> 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 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 was sent by Atlassian JIRA
(v6.1.6#6162)
