[
http://jira.codehaus.org/browse/MDEP-187?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=198438#action_198438
]
Clint Shank commented on MDEP-187:
----------------------------------
My current workaround for this issue is to use the antrun plug-in. For example,
{code:xml}
<plugin>
<artifactId>maven-antrun-plugin</artifactId>
<executions>
<execution>
<!-- copy just built artifact to some lib dir -->
<id>copy-to-lib</id>
<goals>
<goal>run</goal>
</goals>
<phase>package</phase>
<configuration>
<tasks>
<copy
file="${project.build.directory}/${project.build.finalName}.${project.packaging}"
tofile="${some.lib.dir}/${project.artifactId}.${project.packaging}" />
</tasks>
</configuration>
</execution>
</executions>
</plugin>
{code}
This allows "Resolve dependencies from Workspace projects" to work.
> dependency:copy fails when invoked from m2e with workspace resolution enabled
> -----------------------------------------------------------------------------
>
> Key: MDEP-187
> URL: http://jira.codehaus.org/browse/MDEP-187
> Project: Maven 2.x Dependency Plugin
> Issue Type: Bug
> Affects Versions: 2.1
> Reporter: Igor Fedorenko
> Assignee: Brian Fox
> Attachments: MDEP-187.diff, MDEP-187b.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 contact one of the administrators:
http://jira.codehaus.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
