You might want to take a look at the versions plugin (http://mojo.codehaus.org/versions-maven-plugin/) to change the root POM and make the child modules fall in line (update-child-modules goal).
Best maven practice seems to be that you don't try to release part of a hierarchy. If there are modules that shouldn't be released, put them elsewhere (and release them individually or as part of another hierarchy). If there are modules that could be released but needn't be released (because they don't contain changes), it's usually easiest to release them anyway rather then bend yourself backwards. On Tue, Jan 10, 2012 at 9:42 AM, Antonio Petrelli <antonio.petre...@gmail.com> wrote: > 2012/1/10 Glenn Silverman <gsilver...@dispensingsolutionsinc.com> > >> Why not use the >> maven-release-plugin to eliminate the manual process, you might wonder? >> Great, then I have to modify each POMs scm element whenever I do a >> SNAPSHOT-to-RELEASE, and, unless I use module inheritance in my POMs at >> some point, the release plugin isn't going to recurse through all of the >> changed modules for me. >> > > I think you answered yourself. Move to a multi-module POM+. > Moreover, you wrote about a "complex application" made up of several wars, > besides other artifacts. Do you mean that, in the end, you have a single > EAR? > > Antonio --------------------------------------------------------------------- To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
