maven-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Dennis Lundberg (JIRA)" <>
Subject [jira] (MDEPLOY-73) Don't add checksums on gpg signature files
Date Fri, 09 Aug 2013 21:56:52 GMT


Dennis Lundberg commented on MDEPLOY-73:


I've tried out the patch on the maven-2.2.x branch. For uploading it works fine, excluding
the checksums on the signature file. My tries can be seen in our SNAPSHOT repository:

Revision 5 was deployed with Maven 2.2.1 and revision 6 was deployed with a patched Maven

The second part of the patch is for downloading artifacts from the remote repository. AFAICT
Maven do not download .asc files to start with, so there would not be a need to exclude them.
Can anyone comment on that?
> Don't add checksums on gpg signature files
> ------------------------------------------
>                 Key: MDEPLOY-73
>                 URL:
>             Project: Maven Deploy Plugin
>          Issue Type: Improvement
>    Affects Versions: 2.3
>            Reporter: Wendy Smoak
>            Assignee: Olivier Lamy
>            Priority: Minor
>              Labels: contributers-welcome
>             Fix For: 2.8
>         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 is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see:

View raw message