what i've done before is use the versions:use-latest-versions goal in an initial maven invocation and then follow up with clean verify and finally a versions:rollback so that the next svn update does not get borked.
I'd typically have a couple of jobs on the CI server, one building exactly what is in scm, one building with the latest releases and one building with the very latest. If using hudson, you will have to use a freestyle project (which is IMHO the only way to build maven projects in hudson) and have three maven build steps... versions-maven-plugin modifies the pom and so you need to start a new maven process to see the effects -Stephen On 5 October 2010 21:41, Wendy Smoak <wsm...@gmail.com> wrote: > On Tue, Oct 5, 2010 at 4:27 PM, Mike Lenner <mike.len...@gmail.com> wrote: > >> Maybe part of the release process of shared-util should be to update >> some parent pom's dependencyManagement section to the 1.1-SNAPSHOT? > > Or send out a release announcement to their users list, which > project-2's developers should be on? :) > > I believe the versions plugin has a goal that checks for newer > releases of your dependencies, that might be useful. > http://mojo.codehaus.org/versions-maven-plugin/ > > And some of the repository managers (Archiva at least) have feeds you > can watch for updates on artifacts. > > -- > Wendy > > --------------------------------------------------------------------- > To unsubscribe, e-mail: users-unsubscr...@maven.apache.org > For additional commands, e-mail: users-h...@maven.apache.org > > --------------------------------------------------------------------- To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
