note that it will tell you about updates, not whether those updates require a newer version of maven to be used
- Stephen --- Sent from my Android phone, so random spelling mistakes, random nonsense words and other nonsense are a direct result of using swype to type on the screen On 16 Feb 2011 14:16, "chemit" <che...@codelutin.com> wrote: > On Wed, 16 Feb 2011 19:35:07 +0530 > Prashu Negu <prashu.n...@gmail.com> wrote: > >> Hi, >> >> One of the main advantage of Maven is its uniform build system that >> uses centrally located plugins. In our development environment, we >> have base POM where all plugin versions are explicitly mentioned as >> below example. >> >> <plugin> >> <artifactId>maven-compiler-plugin</artifactId> >> <version>2.3.1</version> >> </plugin> >> >> But, there is latest version of this plugin 2.3.2 available which we >> didnt notice. What is the best practice to make sure our build system >> using latest stable plugins apart from manually upgrading versions in >> some common base POM? > > The versions plugin can help you [1] > > Especially, the display-plugin-updates goal tells you which plugin > could be updated [2] : > > So just try a mvn versions:display-plugin-updates > > > [1] http://mojo.codehaus.org/versions-maven-plugin/ > [2] http://mojo.codehaus.org/versions-maven-plugin/display-plugin-updates-mojo.html > > -- > Tony Chemit > -------------------- > tél: +33 (0) 2 40 50 29 28 > email: che...@codelutin.com > http://www.codelutin.com > > --------------------------------------------------------------------- > To unsubscribe, e-mail: users-unsubscr...@maven.apache.org > For additional commands, e-mail: users-h...@maven.apache.org >
