Hi Wouter, Is the top-level POM also the parent pom of the modules? Or only an aggregator?
If it's the parent, then you have to release it [1], because consuming the modules later will require the parent POM as a "dependency" of sorts in order to fully interpolate each module POM. If it's only the aggregator, then I agree with you that releasing it is unnecessary. But I don't have an answer regarding whether that is possible. On the deployment side, it certainly doesn't hurt anything to release it, but from an SVN tagging perspective I see how it could be problematic. To avoid that problem, as a wild guess: maybe you could set suppressCommitBeforeTag [2] to true (and/or other similar configuration flags) in the aggregator, but false in the individual modules? Regards, Curtis [1] Unless you use a trick like the flatten-maven-plugin: http://www.mojohaus.org/flatten-maven-plugin/ [2] http://maven.apache.org/maven-release/maven-release-plugin/prepare-mojo.html#suppressCommitBeforeTag On Thu, Sep 24, 2015 at 5:34 AM, Wouter Lievens <wouter.liev...@cmosis.com> wrote: > First of all, the top-level pom has no real meaning. It just aggregates > the modules, and the "end deliverable" projects (that uses maven-shade to > build an executable jar etc) are among the modules. I take advantage of the > top-level pom's topological sorting of the modules that way, of course. > > Secondly, our SVN repo is set up with tags/trunk/branches per project (so > not at the root), and we use SVN externals to pull all (relevant) projects > into a workspace, which is where the top-level pom sits. In other words, > the top-level pom doesn't have a tags/trunk/branches hierarchy. > > Regards > Wouter > > > ----- Original Message ----- > From: "Jeff MAURY" <jeffma...@gmail.com> > To: "Maven Users List" <users@maven.apache.org> > Sent: Thursday, September 24, 2015 12:28:49 PM > Subject: Re: MRELEASE: Release only modules, not project itself > > What is the problem with releasing the parent pom ? > > Jeff > Le 24 sept. 2015 10:58, "Wouter Lievens" <wouter.liev...@cmosis.com> a > écrit : > > > Hello, > > > > I would like to run the release plugin (prepare/perform) for a top-level > > POM (packaging "pom") that has a big list of modules. > > The top project itself doesn't need to be tagged, released and deployed, > > because it's there only to build the modules in good order. > > So, I want the release plugin run over each module, and only on those > > modules. > > > > Is this possible? Could this be added as a feature? > > > > Best regards, > > Wouter Lievens > > > > > > ------------------------------ > > Wouter Lievens > > Senior Software Architect > > CMOSIS bvba > > Phone +32 3 260 17 58 > > > > --------------------------------------------------------------------- > > 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 > >
