Maven gems: Check those Wicked Dependencies
While building the final 1.0 release for Wicket I needed to see whether all projects use the same version of the Wicket libraries. Using the Maven multiproject plugin I am able to quickly see whether the projects are using the same version of each library.
First you need to check out the projects you want to check into the same workspace:
wicket/ wicket-extensions/ wicket-examples/ wicket-contrib-data/ wicket-contrib-hibernate2/ wicket-contrib-hibernate3/
Then create in the root directory of the workspace two files: project.xml and project.properties. The project.xml file contains the following:
maven-multiproject-plugin
Note that this is not a complete, nor a valid project.xml for serious development using maven.
The project.properties file contains the following properties:
maven.multiproject.basedir=. maven.multiproject.includes=*/project.xml
Now all you need to do is to run:
maven site
in the workspace root folder where you saved the two Maven project files. The resulting report can then be found in the subdirectory: target/docs/dependency-convergence-report.html.
This is one of the gems why I really like Maven as a project management tool.