I dont know what repository you are going against but the default maven repository has 0.7 ( http://mvnrepository.com/artifact/org.apache.clerezza/rdf.jena.tdb.storage). Maybe some developer can help with more detail but what I usually do is use the use-releases goal followed by the use-latest-versions.
Maybe the issue is that 0.7 is not considered a "next" release but the current one by the addon. On 2 Aug 2014 14:21, "Reto Gmür" <r...@apache.org> wrote: > Thanks for the reply. > > The matrix is confusing indeed. > > I tried using use-next-versions as you suggested: > > mvn org.codehaus.mojo:versions-maven-plugin:2.1:use-next-versions > -DgenerateBackupPoms=false -DexcludeReactor=false > > Unfortunately the dependencies remain unchanged, I still have: > > <dependency> > <groupId>org.apache.clerezza</groupId> > <artifactId>rdf.jena.tdb.storage</artifactId> > <scope>runtime</scope> > <version>0.7-SNAPSHOT</version> > </dependency> > > Even though version 0.7 has been released. I'm running in the directory > matching this SCM location: > https://git-wip-us.apache.org/repos/asf?p=clerezza.git;a=tree;f=platform.launcher.tdb;h=4cfa6c98d50256dcc9957bc9ce84aee4f9bcfd98;hb=HEAD > > Cheers, > Reto > > > > On Fri, Aug 1, 2014 at 11:16 PM, Byte Flinger <byteflin...@gmail.com> > wrote: > >> 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" <r...@apache.org> 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 >>> >> > >
