That matrix is a bit confusing. If you look at the description of use-next-releases and use-latest-releases, it says they only modify non-snapshot dependencies and that's what they do. I don't know why the matrix table contradicts that but the description is correct.
If you want to turn a snapshot into release try the use-next-versions and use a latest a versions instead. Keep in mind that they will not downgrade version so if you have a dependency on 1.0.1-SNAPSHOT and the latest release available is 1.0.0 no goal will change that snapshot to release 1.0.0. On 1 Aug 2014 21:06, "Reto Gmür" <[email protected]> wrote: > Hello, > > Looking at the matrix on > http://mojo.codehaus.org/versions-maven-plugin/examples/advancing-dependency-versions.html > I understand that use-next-releases goal does not modify release > dependencies. However running > > mvn org.codehaus.mojo:versions-maven-plugin:2.1:use-latest-releases > -DgenerateBackupPoms=false -DexcludeReactor=false > > result to the following change in the dependencies sections of a pom > > <dependency> > <groupId>xerces</groupId> > <artifactId>xercesImpl</artifactId> > - <version>2.9.1</version> > + <version>2.11.0</version> > </dependency> > > Running: > > mvn org.codehaus.mojo:versions-maven-plugin:2.1:use-latest-versions > -DgenerateBackupPoms=false -DexcludeReactor=false > > Does exactly the same changes as when using the use-latest-releases goal. > > Snapshot dependencies are left unmodified,even though a released version > is available. For example: > > <dependency> > <groupId>org.apache.clerezza.ext</groupId> > <artifactId>org.apache.jena.jena-tdb</artifactId> > <scope>runtime</scope> > <version>1.0.0_1-SNAPSHOT</version> > </dependency> > <dependency> > <groupId>org.apache.clerezza</groupId> > <artifactId>rdf.jena.tdb.storage</artifactId> > <scope>runtime</scope> > <version>0.7-SNAPSHOT</version> > </dependency> > > I'm using maven 3.2.1 but I've also tried 2.2.1. > > Am I misunderstanding something or using it wrongly? > > Cheers, > Reto >
