Whenever I post to the dev list I receive the following mail. Can someone please remove this person from the list to stop this nonsense.

For those of you who can't read French, here's the Babel Fish translation:

  "This notification of state of handing-over is generated automatically."

  "Failure of the delivery to the following addressees."


-------- Original Message --------
Subject: Notification d'=?unicode-1-1-utf-7?Q?+ACs-AOk-tat de remise (+ACs-AOk-chec)?=
Date: Tue, 5 Feb 2008 22:14:58 +ACs-0100
From: postmaster+AEA-adneom.local
To: dennisl+AEA-apache.org

Cette notification d'+AOk-tat de remise est g+AOk-n+AOk-r+AOk-e automatiquement.

+AMk-chec de la remise aux destinataires suivants.

       rgu+AEA-adneom.local





--
Dennis Lundberg
Reporting-MTA: dns;adneomsrv03.adneom.local
Received-From-MTA: dns;adneomsrv03
Arrival-Date: Tue, 5 Feb 2008 22:14:57 +0100

Final-Recipient: rfc822;[email protected]
Action: failed
Status: 5.1.1

--- Begin Message ---
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






--- End Message ---
---------------------------------------------------------------------
To unsubscribe from this list, please visit:

    http://xircles.codehaus.org/manage_email

Reply via email to