On 9/24/2010 3:22 PM, Antonio Petrelli wrote: > 2010/9/24 Marshall Schor <[email protected]>: >> Are you saying that the Maven Release plugin, in particular, has the >> restriction >> that in order for it to work, it the multimodule project has to be the >> parent? > At this point I really don't know, since I always had modules that > have the container as a parent, never tried in another way. > Just a question: when you run release:prepare, does it ask you > versions for every single module?
No, it asks just for versions where I had specified a <dependency> in the top pom. It's as if the release plugin is set up to only work at the top pom, and not run on the modules within (although it does run the build actions on the modules within). I see the release plugin is setup to have its execution inherited by child poms - it has <inheritedByDefault>true</inheritedByDefault> as part of its plugin.xml configuration. Maybe this is why it gets executed on submodules, if those submodules declare the aggregating pom as a "parent". I'm kind of stumped on how to "work around" this. The only thing that comes to mind is to take the Reactor order for all the submodules, and run mvn release on each one, separately, and then change the aggregator pom to no longer do aggregation, but instead, just build the release artifacts (big zips of the various components), using the already "released" parts. -Marshall > Antonio > > --------------------------------------------------------------------- > 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]
