Try running with the -U flag, see if that helps. Force-release goal? Isn't that something that's coming on a future release of the plugin? On 2 Aug 2014 17:20, "Reto Gmür" <r...@apache.org> wrote:
> No luck even with a 2.2-SNAPSHOT version I just compiled. The work around > to first switch back with the new force-release goal and the update the > versions doesn't work as no previous eleased version is available. > > Reto > > > On Sat, Aug 2, 2014 at 4:52 PM, Reto Gmür <r...@apache.org> wrote: > >> Right, I forgot about the use-releases goal. Unfortunately this doesn't >> do it either: >> >> $ mvn org.codehaus.mojo:versions-maven-plugin:2.1:use-releases >> -DgenerateBackupPoms=false -DexcludeReactor=false >> [INFO] Scanning for projects... >> [INFO] >> [INFO] Using the builder >> org.apache.maven.lifecycle.internal.builder.singlethreaded.SingleThreadedBuilder >> with a thread count of 1 >> [INFO] >> >> [INFO] >> ------------------------------------------------------------------------ >> [INFO] Building Clerezza - Platform Launcher with Jena TDB 0.6-SNAPSHOT >> [INFO] >> ------------------------------------------------------------------------ >> [INFO] >> [INFO] --- versions-maven-plugin:2.1:use-releases (default-cli) @ >> platform.launcher.tdb --- >> [INFO] >> ------------------------------------------------------------------------ >> [INFO] BUILD SUCCESS >> [INFO] >> ------------------------------------------------------------------------ >> [INFO] Total time: 2.023 s >> [INFO] Finished at: 2014-08-02T16:39:46+01:00 >> [INFO] Final Memory: 12M/242M >> [INFO] >> ------------------------------------------------------------------------ >> $ git diff >> $ >> >> I'm using maven central. And I'm having the same results even after >> moving my settings.xml away. >> >> The SNAPSHOT dependencies are no longer available. Could this cause the >> problem? >> >> Cheers, >> Reto >> >> >> On Sat, Aug 2, 2014 at 2:42 PM, Byte Flinger <byteflin...@gmail.com> >> wrote: >> >>> 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 >>>>>> >>>>> >>>> >>>> >> >
