updatePolicy "always" does not work for repositories with "releases", at least
not for transitive dependencies
--------------------------------------------------------------------------------------------------------------
Key: MNG-2528
URL: http://jira.codehaus.org/browse/MNG-2528
Project: Maven 2
Issue Type: Bug
Components: Dependencies
Affects Versions: 2.0.4
Reporter: Arne Degenring
Released versions normally should be final. Once deployed, they should not be
upgraded. That's what snapshot versions are for.
Anyway, Maven *does* allow to overwrite an existing version in the repository
by re-deploying it. Therefore, to make builds repeatable and reproducable,
Maven should check for updates even of released versions, not only snapshot
versions.
I tried to use the following setting:
<repositories>
<repository>
<releases>
<enabled>true</enabled>
<updatePolicy>always</updatePolicy>
</releases>
...
My project A has a dependency to version 5.0-SNAPSHOT of a JAR B. That JAR B
has a dependency to version 1.6 of another JAR C. In my local repository
there's an outdated version 1.6 of JAR C (i.e. version 1.6 has been redeployed
after a bug has been found). The problem is: During my build of project A
Maven is looking for an update of JAR B, but NOT of JAR C.
This problem was originally discussed on
http://www.nabble.com/-m2--Updates-of-transitive-dependencies-not-working--tf2158398.html
--
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
