[
https://issues.apache.org/jira/browse/MASSEMBLY-411?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16415169#comment-16415169
]
Tibor Digana commented on MASSEMBLY-411:
----------------------------------------
The same happens when executing the release (mvn release:perform). The assembly
plugin with goal {{{single}} is in the POM. I do not use eclipse m2e plugin in
the POM. The release plugin 2.5.3 is very old but it has to do some hacking
with dependencies on Maven core or assembly plugin. Some kind of influence must
be there.
> Error on copy dependencies using Assembler Plugin (m2e Eclipse Plugin
> Workspace Resolution)
> -------------------------------------------------------------------------------------------
>
> Key: MASSEMBLY-411
> URL: https://issues.apache.org/jira/browse/MASSEMBLY-411
> Project: Maven Assembly Plugin
> Issue Type: Bug
> Components: dependencySet
> Affects Versions: 2.2-beta-3
> Environment: Maven 2.1.0, Eclipse 3.4 Sr2, m2Eclipse 0.9.8
> Reporter: Felipe Desiderati e Souza
> Priority: Major
>
> If you have two projects, with one (B) depending on another (A), and in your
> assembly.xml file you define the following dependencySet:
> {code:xml}
> <dependencySet>
> <outputDirectory>lib/</outputDirectory>
> <scope>runtime</scope>
> <useProjectArtifact>false</useProjectArtifact>
> <useTransitiveDependencies>true</useTransitiveDependencies>
> </dependencySet>
> {code}
> And the workspace resolution been activated, during the package phase an
> error will occur showing that is not possible to copy the "target/classes"
> file from project A. Because "target/classes" isn't a file. This error only
> occurs if the workspace resolution is enabled.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
