Jens Riboe wrote:
As I understand it; the current rule implements implicit URLs as
${parent.url}/${project.artifactId}
For example:
<scm>
<connection>${parentPOM.scm.connection}/${project.artifactId}</connection>
...
/scm>
Where parentPOM is a made-up symbol denoting an upward search for the
pom property that follows (scm.connection).
So, how about the following suggestion:
The Super POM contains this kind of definition for all URLs where this
rule applies today. When the effective POM
is computed for a sub-project it uses the "closest" url definition that
contains the symbol parentPOM. If none is
found expect the def in super pom, this one is used and the rule applies
as it always has.
This will break existing builds.
The maven inheritance mechanism will not take the parent pom into
consideration if you say something like
> <connection>scm:cvs:[EMAIL PROTECTED]:/yyy</connection>
because this is considered as a fixed string and thus overrides the
value from the parent. Maven only inherits values from parent POMs when
the tags are non-existing in the child pom or in special cases likes
plugin configurations from pluginManagement or plugin executions with
the same id.
Stefan
--
best regards,
Stefan Seidel
software developer
________________________
VUB Printmedia GmbH
Chopinstraße 4
D-04103 Leipzig
Germany
tel. +49 (341) 9 60 50 07
fax. +49 (341) 9 60 50 92
mail. [EMAIL PROTECTED]
web. www.vub.de
HRB Köln 24015
UStID DE 122 649 251
GF Dr. Achim Preuss Neudorf,
Dr. Christian Preuss Neudorf
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
