maven-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Dennis Lundberg (JIRA)" <j...@codehaus.org>
Subject [jira] (MNG-5504) Don't add checksums on gpg signature files
Date Tue, 13 Aug 2013 18:32:52 GMT

     [ https://jira.codehaus.org/browse/MNG-5504?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]

Dennis Lundberg moved MDEPLOY-73 to MNG-5504:
---------------------------------------------

           Complexity: Intermediate
        Fix Version/s:     (was: 2.8)
    Affects Version/s:     (was: 2.3)
                       2.2.1
                       3.0.5
                       3.1.0
                  Key: MNG-5504  (was: MDEPLOY-73)
              Project: Maven 2 & 3  (was: Maven Deploy Plugin)
    
> Don't add checksums on gpg signature files
> ------------------------------------------
>
>                 Key: MNG-5504
>                 URL: https://jira.codehaus.org/browse/MNG-5504
>             Project: Maven 2 & 3
>          Issue Type: Improvement
>    Affects Versions: 3.1.0, 3.0.5, 2.2.1
>            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 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

Mime
View raw message