Does it work if you are not using the central repo directly but a repository manager (archiva in my case) in between. Will this plugin "see" the newer versions, even if they are not in archiva yet?
regards, Wim 2008/9/5 Stephen Connolly <[EMAIL PROTECTED]> > The Mojo team is pleased to announce the release of the Versions Maven > Plugin, version 1.0-alpha-1. > > This plugin allows: > * the querying for newer versions of plugins used in a project. > * the querying for newer versions of dependencies used in a project. > * updating a project's parent to the latest available version > (e.g. useful for syncing with corporate poms to ensure the latest is > used prior to rolling a release) > * updating properties defined in a project to the latest version of a > specific > artifact (e.g. for ensuring that a suite of dependencies are all the same > version) > > http://mojo.codehaus.org/versions-maven-plugin/ > > You can run mvn -up to get the latest version of the plugin, or specify > the version in your project's plugin configuration: > > <plugin> > <groupId>org.codehaus.mojo</groupId> > <artifactId>versions-maven-plugin</artifactId> > <version>1.0-alpha-1</version> > </plugin> > > Release Notes - Maven 2.x Versions Plugin - Version 1.0-alpha-1 > > ** Bug > * [MVERSIONS-1] - javadoc plugin doesn't have its version specified but > it has > * [MVERSIONS-2] - display-plugin-updates does not include lifecycle > plugins that are not defined in the pom. > > ** Known Issues - Maven 2.x Versions Plugin - Version 1.0-alpha-1 > * [MVERSIONS-3] - display-plugin-updates does not identify the plugin > version as not being provided when derived from the super-pom > > Enjoy, > > -The Mojo team >
