You may be interested in these related issues: http://jira.codehaus.org/browse/MNG-3092 http://jira.codehaus.org/browse/MNG-2994
Cheers, Mark 2008/9/16 Borut Bolčina <[EMAIL PROTECTED]>: > Hi list, > > using ranges for artifact resolution we achieved the goal of always > resolving the latest version of modules. We decided to use ranges because > the modules are released on a daily/week interval and nobody wants to raise > versions in a great number of poms which are using them. We have two > profiles - one picking dependencies only from release repos and one picking > from snapshots repos also, so if one needs snapshot versions of jars, it > builds with a profile which includes snapshots repos (virtual repo in > Artifactory). > > But there is a catch. If for example there are these versions deployed to > the Artifactory: > myJar-1.0.0.jar > myJar-1.0.0-SNAPSHOT.jar > myJar-1.1.0-SNAPSHOT.jar > > and all of these are also in user's local repo, then when trying to do a > release:prepare with the default profile which does not include snapshots > repos, the release fails because the latest version is of course > myJar-1.1.0-SNAPSHOT.jar. The "workaround" is manually deleting the > myJar-1.1.0-SNAPSHOT.jar from the local repo and re-run the release:prepare > which of course correctly takes myJar-1.0.0.jar. > > Is there an option or a way to tell maven to ignore local versions? > > Regards, > Borut >
