thanks Stephen, what command do you past to maven, just mvn versions:update-properties? Im using for maven 2.0.10 for other internal reasons with a multi module maven project.
Thanks, Andy 2010/1/27 Stephen Connolly <[email protected]> > strange because it works for me! > > 2010/1/27 Andy Richards <[email protected]> > > Hi all, >> >> Can anyone advise how I can make the versions:-update-properties command >> refer to a snapshot version which is deployed only into my local repository >> and which isn't a "released" snapshot? The versions:-update-properties >> command does exactly what I want but always seems to use the release version >> of a dependency installed locally and also in our artifactory repository. >> The snaphot i want to depend on isn’t a snapshot release as the company i >> work for do not release snapshots into artifactory so I just want to include >> a local snapshot release if possible? >> >> Ive tried everything on the versions:-update-properties examples page, >> does anyone know how to do this? >> >> I have the following defined in my parent pom... >> >> <logging.version>1.2</logging.version> >> ..... >> <plugin> >> <groupId>org.codehaus.mojo</groupId> >> <artifactId>versions-maven-plugin</artifactId> >> <version>1.1</version> >> <configuration> >> <allowSnapshots>true</allowSnapshots> >> <properties> >> <property> >> <name>logging.version</name> >> </property> >> </properties> >> </configuration> >> </plugin> >> >> However the maven console always logs that its is using version 1.2 when >> version 1.3-SNAPSHOT exists in my local repository. >> >> Any help much appreciated, >> >> Many thanks, >> >> Andy. >> >> > >
