You are viewing a plain text version of this content. The canonical link for it is here.

Posted to issues@maven.apache.org by "Daniel Kulp (JIRA)" <ji...@codehaus.org> on 2009/05/05 17:55:44 UTC

[jira] Commented: (MGPG-14) With maven 2.1.0 some poms end up with invalid signatures

    [ http://jira.codehaus.org/browse/MGPG-14?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=175162#action_175162 ] 

Daniel Kulp commented on MGPG-14:
---------------------------------


The attached patch seems to work fine for Maven 2.1.0 and 2.0.9.     However, there is a little bit of "hackish" code in there that's I'd like some others to look at before I commit it.


> With maven 2.1.0 some poms end up with invalid signatures
> ---------------------------------------------------------
>
>                 Key: MGPG-14
>                 URL: http://jira.codehaus.org/browse/MGPG-14
>             Project: Maven 2.x GPG Plugin
>          Issue Type: Bug
>    Affects Versions: 1.0-alpha-4
>            Reporter: Daniel Kulp
>         Attachments: patch.txt, patch2.txt
>
>
> The pom-transformed.xml is installed, but gpg is signing the original pom.xml.   Thus, the signature is invalid.

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira