display-dependency-updates goal now added The display-dependency-updates goal will check all the dependencies used in your project and display a list of those dependencies with newer versions available.
Here are some examples of what this looks like: svn checkout http://svn.codehaus.org/mojo/trunk/mojo/build-helper-maven-plugin build-helper-maven-plugin cd build-helper-maven-plugin mvn versions:display-dependency-updates Which produced the following output: [INFO] ------------------------------------------------------------------------ [INFO] Building Build Helper Maven Plugin [INFO] task-segment: [versions:display-plugin-updates] [INFO] ------------------------------------------------------------------------ [INFO] [versions:display-plugin-updates] [INFO] [INFO] The following dependency updates are available: [INFO] org.apache.maven:maven-artifact ........................ 2.0 -> 2.0.9 [INFO] org.apache.maven:maven-plugin-api ...................... 2.0 -> 2.0.9 [INFO] org.apache.maven:maven-project ....................... 2.0.2 -> 2.0.9 [INFO] org.codehaus.plexus:plexus-utils ....................... 1.1 -> 1.5.6 [INFO] [INFO] ------------------------------------------------------------------------ [INFO] BUILD SUCCESSFUL [INFO] ------------------------------------------------------------------------ [INFO] Total time: 17 seconds [INFO] Finished at: Fri Aug 15 10:46:03 IST 2008 [INFO] Final Memory: 10M/167M [INFO] ------------------------------------------------------------------------ On Fri, Aug 15, 2008 at 10:03 AM, Mark Hobson <[EMAIL PROTECTED]> wrote: > 2008/8/15 Stephen Connolly <[EMAIL PROTECTED]>: > > I have plans for that too!!! > > > > I want one goal that looks at all the projects in the reactor and ensures > > they are all using the same versions of dependencies external to the > > reactor. > > > > I want another goal that looks ate all the projects in the reactor and > > ensures they are depending on the reactor versions... for example if you > > have checked out log4j and are working on a custom version of it, and > this > > custom version is a project in your reactor... then this goal would look > at > > all the other projects in your reactor, and if they are depending on any > > version of log4j, it will switch them to the version in your reactor. > > > > If I get really fancy, I may have a try-plugin-updates and > > try-dependency-updates goal which relies on your build's tests to see if > the > > dependencies can be updated... > > > > That goal would look and see that your project depends on log4j 1.2.5, it > > will start with a "clean verify" to check that all unit and integration > > tests are passing. Then it will try the latest log4j and run "clean > verify" > > moving back one version at a time if the build fails... Then you iterate > > through all dependencies until you can make no more changes... of course > > that could take some time!!! > > I like, keep up the good work :) > > Mark > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED] > >
