I have a similar issue with the versions:display-dependency-updates goal. It is not reporting updates for snapshots, maybe the issues are related.
Running the following when I have a snapshot version of the first dependency In my (local) repository mvn -DallowSnapshots=true versions:display-dependency-updates I get, The following dependencies in Dependencies are using the newest version: com.serco.tf.util:tf-util-common ............................... 4.0.0 jboss.client:jboss-annotations-ejb3 ............................ 4.2.1 jboss.client:jboss-ejb3x ....................................... 4.2.1 jboss.client:jboss-j2ee ........................................ 4.2.1 log4j:log4j ................................................... 1.2.14 oracle:ojdbc14 ............................................ 10.2.0.2.0 The following dependencies in Dependencies have newer versions: junit:junit ............................................... 4.1 -> 4.4 And when I add a non snapshot version I get The following dependencies in Dependencies are using the newest version: jboss.client:jboss-annotations-ejb3 ............................ 4.2.1 jboss.client:jboss-ejb3x ....................................... 4.2.1 jboss.client:jboss-j2ee ........................................ 4.2.1 log4j:log4j ................................................... 1.2.14 oracle:ojdbc14 ............................................ 10.2.0.2.0 The following dependencies in Dependencies have newer versions: com.serco.tf.util:tf-util-common ...................... 4.0.0 -> 4.1.0 junit:junit ............................................... 4.1 -> 4.4 This is with maven 2.2.1 Cheers, Vic -- Victor Kirk Analyst Transportation Systems - Network Services Serco Cavendish House Clearwater Park Prince's Wharf Stockton-on-Tees TS17 6QY Tel: +44 (0)1642 636894 From: Stephen Connolly [mailto:[email protected]] Sent: 27 January 2010 13:13 To: [email protected] Subject: Re: [mojo-user] versions:-update-properties & local repository SNAPSHOTS mvn versions:update-properties -DallowSnapshots=true 2010/1/27 Andy Richards <[email protected]> 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. ______________________________________________________________________ This email has been scanned by the MessageLabs Email Security System. For more information please visit http://www.messagelabs.com/email ______________________________________________________________________ --------------------------------------------------------------------- To unsubscribe from this list, please visit: http://xircles.codehaus.org/manage_email
