[ https://jira.codehaus.org/browse/MANTTASKS-234?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=314899#comment-314899
]
Justin Rowe commented on MANTTASKS-234:
---------------------------------------
This is worse than I thought, because it actually downloads the first (i.e. oldest) version
of the snapshot, rather than the latest version. This is in contrast to mvn org.apache.maven.plugins:maven-dependency-plugin:2.4:get
which correctly downloads the latest version; this is the behaviour that I would expect.
> artifact:dependencies does not download latest version SNAPSHOT dependency if already
present locally
> -----------------------------------------------------------------------------------------------------
>
> Key: MANTTASKS-234
> URL: https://jira.codehaus.org/browse/MANTTASKS-234
> Project: Maven 2.x Ant Tasks
> Issue Type: Bug
> Components: dependencies task
> Affects Versions: 2.1.3
> Environment: Windows
> Reporter: Justin Rowe
>
> We are using <artifact:dependencies> to trigger download of an artifact from a
remote repo to the local repo. When the dependency is a SNAPSHOT dependency, it only seems
to check that the dependency exists in the local repo, it does not check that there is a more
recent snapshot in the remote repo. So the snapshot artifact does not get updated with the
latest version.
> My workaround is to call this artifact:dependencies, delete the artifact that is referred
to in the property that gets set by this task, and then call artifact:dependencies again to
ensure that we have the correct version.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://jira.codehaus.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
|