I have to correct my own email. The behavior here is independent of
relativePath and the presence or absence of modules. As things are
now, a pom like the global asf or maven pom dare not have a site
declared, or it will interact with poms that use it as a parent, even
if those poms fully specify the distribution management for site.
On Thu, Jul 28, 2011 at 7:06 AM, Benson Margulies bimargul...@gmail.com wrote:
I think that there's a general principle at work in MSITE-600, so I
wonder whether anyone else agrees.
Quick summary:
Pom 1 has a distributionManagement/site/url element and a
modules/module element.
Pom 2 has a parent that indicates pom 1, with a relativePath. it also
has a distribution/site/url element.
My view is that a child value should override a parent value, period,
unless some other mechanism (c.f. the attributes on plugin
configuration elements) states otherwise.
The current implementation of the trunk of m-s-p is that the values in
the child and parent should be combined if there's a relativePath that
reaches the parent, even if the parent isn't in the reactor.
More details are available in the JIRA.
-
To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org
For additional commands, e-mail: dev-h...@maven.apache.org
