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" <[email protected]> To: "Maven Users List" <[email protected]> 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" <[email protected]> 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: [email protected] > For additional commands, e-mail: [email protected] > > --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
