If you are prepared to run maven multiple times as part of your CI build you could achieve some of what you are looking for with the versions-maven-plugin.
step 1. use versions-maven-plugin to update the pom to the latest releases of all dependencies step 2. use maven-scm-plugin to commit the modified poms back to scm step 3. use maven-release-plugin to release the ci build (the following 2 steps are optional) step 4. use versions-maven-plugin to update the pom to the next snapshots of all dependencies step 5 . use maven-scm-plugin to commit the modified poms back to scm ok, so you're ci build will auto-generate tags... but if you root ci generated tags in a special ci-tags directory and only do these 3/5 step builds nightlly it should be less of an SCM churn -Stephen 2009/4/6 Hayes, Peter <peter.ha...@fmr.com> > Graham Leggett wrote: > > >Having said that, it makes no sense to have the release plugin care > >about LATEST, because by definition, building against LATEST isn't > >repeatable, and in order for there to be a release, you need the build > >to be repeatable. > > I think this does impact the release plugin as it could offer the ability > to resolve the LATEST version at release time. These builds would be > reproducible because the release plugin tags the poms during the release > process. > > I think what you're saying is that the build prior to the release build is > not guaranteed to have the same dependent artifacts as the release build. I > care about the release build being reproducible. > > Pete >
