You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@maven.apache.org by "Udo Schnurpfeil (JIRA)" <ji...@codehaus.org> on 2015/03/21 12:14:18 UTC
[jira] (MNG-5504) Don't add checksums on gpg signature files
[ https://jira.codehaus.org/browse/MNG-5504?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=365510#comment-365510 ]
Udo Schnurpfeil commented on MNG-5504:
--------------------------------------
Hi,
I just want to test the patch, but it turns out that 3.3.1 hasn't this bug any longer.
3.2.3 has the bug, but I didn't find the code of the fix.
Nevertheless, this can be closed?
> Don't add checksums on gpg signature files
> ------------------------------------------
>
> Key: MNG-5504
> URL: https://jira.codehaus.org/browse/MNG-5504
> Project: Maven
> Issue Type: Improvement
> Affects Versions: 2.2.1, 3.0.5, 3.1.0
> Reporter: Wendy Smoak
> Assignee: Olivier Lamy
> Priority: Minor
> Labels: contributers-welcome
> Attachments: DefaultWagonManager.patch
>
>
> Similar to MINSTALL-48, don't create checksums when deploying a gpg signature file along with the artifact.
> Currently we end up with filename.asc, filename.asc.md5 and filename.asc.sha1 in the remote repository, and only filename.asc is necessary.
--
This message was sent by Atlassian JIRA
(v6.1.6#6162)