You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@archiva.apache.org by "Wendy Smoak (JIRA)" <ji...@codehaus.org> on 2009/06/02 22:33:42 UTC
[jira] Created: (MRM-1196) checksums are not updated when artifact
is re-uploaded
checksums are not updated when artifact is re-uploaded
------------------------------------------------------
Key: MRM-1196
URL: http://jira.codehaus.org/browse/MRM-1196
Project: Archiva
Issue Type: Bug
Affects Versions: 1.2.1
Reporter: Wendy Smoak
If you upload a jar through the web interface, Archiva correctly generates md5 and sha1 checksums for the jar and pom.
If you re-upload the same artifact, (perhaps you accidentally uploaded the wrong jar, or need to fix something in the pom,) Archiva does not generate new checksums.
This causes multiple downloads and warning during Maven builds.
To reproduce, upload any jar as com.example:example:1.0 and verify the checksums:
$ md5sum -c example-1.0.jar.md5
example-1.0.jar: OK
$ sha1sum -c example-1.0.jar.sha1
example-1.0.jar: OK
Then upload a different jar with the same parameters. Verify the checksums, and you'll see:
$ md5sum -c example-1.0.jar.md5
example-1.0.jar: FAILED
md5sum: WARNING: 1 of 1 computed checksum did NOT match
$ sha1sum -c example-1.0.jar.sha1
example-1.0.jar: FAILED
sha1sum: WARNING: 1 of 1 computed checksum did NOT match
This also happens if you upload a new pom.
A workaround is to delete the artifact before uploading the replacement. Then Archiva will generate the checksums correctly.
--
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: (MRM-1196) checksums are not updated when artifact
is re-uploaded
Posted by "Maria Odea Ching (JIRA)" <ji...@codehaus.org>.
[ http://jira.codehaus.org/browse/MRM-1196?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Maria Odea Ching updated MRM-1196:
----------------------------------
Assignee: Maria Odea Ching
Fix Version/s: 1.2.2
> checksums are not updated when artifact is re-uploaded
> ------------------------------------------------------
>
> Key: MRM-1196
> URL: http://jira.codehaus.org/browse/MRM-1196
> Project: Archiva
> Issue Type: Bug
> Affects Versions: 1.2.1
> Reporter: Wendy Smoak
> Assignee: Maria Odea Ching
> Fix For: 1.2.2
>
>
> If you upload a jar through the web interface, Archiva correctly generates md5 and sha1 checksums for the jar and pom.
> If you re-upload the same artifact, (perhaps you accidentally uploaded the wrong jar, or need to fix something in the pom,) Archiva does not generate new checksums.
> This causes multiple downloads and warning during Maven builds.
> To reproduce, upload any jar as com.example:example:1.0 and verify the checksums:
> $ md5sum -c example-1.0.jar.md5
> example-1.0.jar: OK
> $ sha1sum -c example-1.0.jar.sha1
> example-1.0.jar: OK
> Then upload a different jar with the same parameters. Verify the checksums, and you'll see:
> $ md5sum -c example-1.0.jar.md5
> example-1.0.jar: FAILED
> md5sum: WARNING: 1 of 1 computed checksum did NOT match
> $ sha1sum -c example-1.0.jar.sha1
> example-1.0.jar: FAILED
> sha1sum: WARNING: 1 of 1 computed checksum did NOT match
> This also happens if you upload a new pom.
> A workaround is to delete the artifact before uploading the replacement. Then Archiva will generate the checksums correctly.
--
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] Closed: (MRM-1196) checksums are not updated when artifact
is re-uploaded
Posted by "Maria Odea Ching (JIRA)" <ji...@codehaus.org>.
[ http://jira.codehaus.org/browse/MRM-1196?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Maria Odea Ching closed MRM-1196.
---------------------------------
Resolution: Fixed
Fixed in trunk -r783687.
> checksums are not updated when artifact is re-uploaded
> ------------------------------------------------------
>
> Key: MRM-1196
> URL: http://jira.codehaus.org/browse/MRM-1196
> Project: Archiva
> Issue Type: Bug
> Affects Versions: 1.2.1
> Reporter: Wendy Smoak
> Assignee: Maria Odea Ching
> Fix For: 1.2.2
>
>
> If you upload a jar through the web interface, Archiva correctly generates md5 and sha1 checksums for the jar and pom.
> If you re-upload the same artifact, (perhaps you accidentally uploaded the wrong jar, or need to fix something in the pom,) Archiva does not generate new checksums.
> This causes multiple downloads and warning during Maven builds.
> To reproduce, upload any jar as com.example:example:1.0 and verify the checksums:
> $ md5sum -c example-1.0.jar.md5
> example-1.0.jar: OK
> $ sha1sum -c example-1.0.jar.sha1
> example-1.0.jar: OK
> Then upload a different jar with the same parameters. Verify the checksums, and you'll see:
> $ md5sum -c example-1.0.jar.md5
> example-1.0.jar: FAILED
> md5sum: WARNING: 1 of 1 computed checksum did NOT match
> $ sha1sum -c example-1.0.jar.sha1
> example-1.0.jar: FAILED
> sha1sum: WARNING: 1 of 1 computed checksum did NOT match
> This also happens if you upload a new pom.
> A workaround is to delete the artifact before uploading the replacement. Then Archiva will generate the checksums correctly.
--
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