[
https://jira.codehaus.org/browse/MANTTASKS-237?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=325532#comment-325532
]
Thomas Pasch commented on MANTTASKS-237:
----------------------------------------
MANTTASKS-234 also reports problems with <artifact:dependencies/> but has
different findings.
MANTTASKS-233 suggests to use a more recent version of the
maven-dependency-plugin (and mvn3). MANTTASKS-232 suggests to use mvn3
(instead of mvn2). I would consent to both (and I guess that the problem
reported here would be gone with this change(s)).
As a workaround one could use the
[dependency:copy|https://maven.apache.org/plugins/maven-dependency-plugin/copy-mojo.html]
task from the maven-dependency-plugin directly. But this is more or less the
advice to abstain from using Maven 2.x Ant Tasks completely.
> <artifact:dependencies/> Task only checks Maven Repo Servers
> ------------------------------------------------------------
>
> Key: MANTTASKS-237
> URL: https://jira.codehaus.org/browse/MANTTASKS-237
> Project: Maven 2.x Ant Tasks
> Issue Type: Bug
> Components: dependencies task
> Affects Versions: 2.1.3
> Environment: Ubuntu Raring/13.04 64bit, but most probably OS
> independant
> Reporter: Thomas Pasch
> Priority: Minor
>
> <artifact:dependencies/> Task only checks Maven Repo Servers. This is wrong
> and best seen with SNAPSHOT dependencies.
> The dependency task should (also) take into account (in this proper sequence):
> 1. The current maven reactor, i.e. the modules to build currently. (This
> should be none, as the dependency task rather will build nothing.)
> 2. The local maven artifact cache (normally situated under ~/.m2/repository.
> 3. The repo servers defined in the pom.xml (and the default repo servers).
> (This is the only thing done currently.)
>
--
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
