You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@maven.apache.org by "Wendy Smoak (JIRA)" <ji...@codehaus.org> on 2008/02/23 16:35:28 UTC

[jira] Created: (MDEPLOY-73) Don't add checksums on gpg signature files

Don't add checksums on gpg signature files
------------------------------------------

                 Key: MDEPLOY-73
                 URL: http://jira.codehaus.org/browse/MDEPLOY-73
             Project: Maven 2.x Deploy Plugin
          Issue Type: Wish
    Affects Versions: 2.3
            Reporter: Wendy Smoak
            Priority: Minor


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 contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira

        

[jira] Updated: (MDEPLOY-73) Don't add checksums on gpg signature files

Posted by "Wendy Smoak (JIRA)" <ji...@codehaus.org>.
     [ http://jira.codehaus.org/browse/MDEPLOY-73?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Wendy Smoak updated MDEPLOY-73:
-------------------------------

    Patch Submitted: [Yes]

> Don't add checksums on gpg signature files
> ------------------------------------------
>
>                 Key: MDEPLOY-73
>                 URL: http://jira.codehaus.org/browse/MDEPLOY-73
>             Project: Maven 2.x Deploy Plugin
>          Issue Type: Wish
>    Affects Versions: 2.3
>            Reporter: Wendy Smoak
>            Priority: Minor
>         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 contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira

        

[jira] Commented: (MDEPLOY-73) Don't add checksums on gpg signature files

Posted by "SebbASF (JIRA)" <ji...@codehaus.org>.
    [ http://jira.codehaus.org/browse/MDEPLOY-73?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=217865#action_217865 ] 

SebbASF commented on MDEPLOY-73:
--------------------------------

I think this should be classified as a bug, rather than a wish.

> Don't add checksums on gpg signature files
> ------------------------------------------
>
>                 Key: MDEPLOY-73
>                 URL: http://jira.codehaus.org/browse/MDEPLOY-73
>             Project: Maven 2.x Deploy Plugin
>          Issue Type: Wish
>    Affects Versions: 2.3
>            Reporter: Wendy Smoak
>            Priority: Minor
>         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 contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira

        

[jira] Updated: (MDEPLOY-73) Don't add checksums on gpg signature files

Posted by "Oleg Estekhin (JIRA)" <ji...@codehaus.org>.
     [ http://jira.codehaus.org/browse/MDEPLOY-73?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Oleg Estekhin updated MDEPLOY-73:
---------------------------------

    Attachment: DefaultWagonManager.patch

> Don't add checksums on gpg signature files
> ------------------------------------------
>
>                 Key: MDEPLOY-73
>                 URL: http://jira.codehaus.org/browse/MDEPLOY-73
>             Project: Maven 2.x Deploy Plugin
>          Issue Type: Wish
>    Affects Versions: 2.3
>            Reporter: Wendy Smoak
>            Priority: Minor
>         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 contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira

        

[jira] Commented: (MDEPLOY-73) Don't add checksums on gpg signature files

Posted by "Oleg Estekhin (JIRA)" <ji...@codehaus.org>.
    [ http://jira.codehaus.org/browse/MDEPLOY-73?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=210620#action_210620 ] 

Oleg Estekhin commented on MDEPLOY-73:
--------------------------------------

On deployment the .md5 and .sha1 files are added by the org.apache.maven.artifact.manager.DefaultWagonManager in the putRemoteFile() method.

The attached patch modifies the putRemoteFile() method so it will not create .asc.md5 and .asc.sha1 when uploading .asc file, and getRemoteFile() method so it will not check checksums when downloading .asc file.

The diff is against http://svn.apache.org/repos/asf/maven/maven-2/branches/maven-2.2.x.

> Don't add checksums on gpg signature files
> ------------------------------------------
>
>                 Key: MDEPLOY-73
>                 URL: http://jira.codehaus.org/browse/MDEPLOY-73
>             Project: Maven 2.x Deploy Plugin
>          Issue Type: Wish
>    Affects Versions: 2.3
>            Reporter: Wendy Smoak
>            Priority: Minor
>         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 contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira

        

[jira] (MDEPLOY-73) Don't add checksums on gpg signature files

Posted by "Olivier Lamy (JIRA)" <ji...@codehaus.org>.
     [ https://jira.codehaus.org/browse/MDEPLOY-73?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Olivier Lamy updated MDEPLOY-73:
--------------------------------

    Fix Version/s: 2.8
         Assignee: Olivier Lamy
       Issue Type: Improvement  (was: Wish)
    
> Don't add checksums on gpg signature files
> ------------------------------------------
>
>                 Key: MDEPLOY-73
>                 URL: https://jira.codehaus.org/browse/MDEPLOY-73
>             Project: Maven 2.x and 3.x 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: https://jira.codehaus.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira