Oh, that's what I thought. But someone sent me a debug output (-X) of a release build of a multi module project.
Each module has it's own (incorrectly rewritten) scm section. I assumed that it was there in the original poms. I've been told that they are not. So, in that case, where are the additional scm sections coming from (unless I've been lied too)? Are they meant to be there? (In the effective pom for each module - as displayed in the -X output)? -Chris On Fri, Feb 17, 2012 at 12:44 AM, Stephen Connolly < [email protected]> wrote: > Afaik there is that tag per module option which might be a sort of > support... But other than if that might happen to work, no support... Think > about it, if a child module's Pom is not in the parent's checkout, the > build will fail (unless you cheat with file based profile activation to add > in the module to the reactor when present) > > On Thursday, 16 February 2012, Chris Graham <[email protected]> wrote: > > Hi all. > > > > What is the behavior of the release plugin if, in a multi-module project > each sub module has it's own SCM section and points to a different SCM URL > location? > > > > Is this supported? (I didn't think that it was.) > > > > -Chris > > > > Sent from my iPhone > > --------------------------------------------------------------------- > > To unsubscribe, e-mail: [email protected] > > For additional commands, e-mail: [email protected] > > > > >
