[
https://jira.codehaus.org/browse/MDEPLOY-73?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=330432#comment-330432
]
Dennis Lundberg commented on MDEPLOY-73:
----------------------------------------
Hi,
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:
https://repository.apache.org/content/repositories/snapshots/org/apache/maven/shared/maven-mapping/1.0-SNAPSHOT/
Revision 5 was deployed with Maven 2.2.1 and revision 6 was deployed with a
patched Maven 2.2.2-RC1-SNAPSHOT.
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: https://jira.codehaus.org/browse/MDEPLOY-73
> 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: http://www.atlassian.com/software/jira
