Jerome Lacoste wrote:
On Feb 4, 2008 7:31 PM, Dennis Lundberg <[EMAIL PROTECTED]> wrote:
You need to define an scm element in keytool-maven-plugin's pom.xml. The
inherited values are inherited, but has the wrong values.
The released parent mojo POM contains the references to the scm tag.
Yes, to the release tag of the parent pom. But that is in another part
of the subversion tree.
Is this expected behavior (and in that case conflicts with the
inheritance of the <scm> POM section that doesn't take tags into
account) ?
The <scm> element of the pom is inherited from the parent if a project
doesn't provide one itself. The inherited scm URL is the URL of the
parent with "/project-artifactId" appended to it. This is not what we
want in this case.
Or is this a bug in the release plugin ?
No, not a bug, I'd say that it's a feature that is missing. The release
plugin's current way of inheriting <scm> elements works well for a
multi-module build. It doesn't work well for the
parent-pom-in-a-separate-scm-location-with-completely-different-release-cycle
use case.
I understand that we might want to point to the exact scm tag in the
documentation, but if that breaks POM inheritance.
Once the <scm> element is added, then this is handled transparently by
the release-plugin.
J
---------------------------------------------------------------------
To unsubscribe from this list, please visit:
http://xircles.codehaus.org/manage_email
--
Dennis Lundberg
---------------------------------------------------------------------
To unsubscribe from this list, please visit:
http://xircles.codehaus.org/manage_email
