There is a release to move up. I haven't deployed a 15.3.60, but I do have a 15.3.60-1. It should be picking that up.
On Fri, May 13, 2011 at 9:04 PM, Stephen Connolly < [email protected]> wrote: > has 15.6.30 been released yet? > > has a newer version been released yet? > > v-m-p does not go backwards - ever - on the basis that newer versions > should be backward compatible, but older versions most likely will not. > > If there is no release to move up to, then it will leave it alone > > -Stephen > > > On 13 May 2011 22:08, Worm Man <[email protected]> wrote: > >> Hi. >> >> I'm trying this plugin and i don't know if I'm doing anything wrong, but >> it won't work for me. I'm using Artifactory, but i can see correct metadata >> even on my local repository. >> I have a very simple POM with a snapshot dependency inside: >> >> <dependencies> >> <dependency> >> <groupId>com.dummy</groupId> >> <artifactId>dummy-client</artifactId> >> <version>15.6.30-SNAPSHOT</version> >> </dependency> >> </dependencies> >> >> When I execute: mvn versions:use-releases, it does nothing. >> >> If I enable the debugging log level, I can see this: >> [DEBUG] Looking for a release of >> com.dummy:dummy-client:jar:null:15.6.30-SNAPSHOT >> [DEBUG] Determining update check for artifact com.dummy:dummy-client >> (/home/user/.m2/repository/com/dummy/dummy-client/maven-metadata-artifactory.xml) >> from artifactory ( >> http://artifactoryserver.domain.com:8080/artifactory/all) >> [DEBUG] Searching for >> artifactory.maven-metadata-artifactory.xml.lastUpdated in resolution >> tracking file. >> [DEBUG] Reading resolution-state from: >> /home/user/.m2/repository/com/dummy/dummy-client/resolver-status.properties >> >> There's nothing changed. The POM is not created and no backup file is >> created. >> Could you tell me what could be going wrong? >> Thanks. >> >> Regards. >> > >
