You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@maven.apache.org by "Etienne Dube (JIRA)" <ji...@codehaus.org> on 2009/07/11 14:37:22 UTC
[jira] Created: (MAVENUPLOAD-2513) bad md5 / sha1 files in
commons-pool-1.3
bad md5 / sha1 files in commons-pool-1.3
----------------------------------------
Key: MAVENUPLOAD-2513
URL: http://jira.codehaus.org/browse/MAVENUPLOAD-2513
Project: Maven Upload Requests
Issue Type: Bug
Reporter: Etienne Dube
Hi, not sure if it is the right place to report this problem but I haven't found anywhere else.
Some md5 and sha1 hash files don't have the right format in http://repo1.maven.org/maven2/commons-pool/commons-pool/1.3/
The culprits are commons-pool-1.3-sources.jar.md5 and commons-pool-1.3-sources.jar.sha1. For example:
SHA1(commons-pool-1.3-sources.jar)= 97f4c4b0144792c8173199cec14c3948c91aff81
The leading "SHA1(commons-pool-1.3-sources.jar)= " string causes mvn or ivy to fail with an "invalid sha1" error when downloading commons-pool-1.3-sources.jar
Thanks
--
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: (MEV-628) bad md5 / sha1 files in commons-pool-1.3
Posted by "Benjamin Bentmann (JIRA)" <ji...@codehaus.org>.
[ http://jira.codehaus.org/browse/MEV-628?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Benjamin Bentmann updated MEV-628:
----------------------------------
Component/s: Checksum Failure
> bad md5 / sha1 files in commons-pool-1.3
> ----------------------------------------
>
> Key: MEV-628
> URL: http://jira.codehaus.org/browse/MEV-628
> Project: Maven Evangelism
> Issue Type: Bug
> Components: Checksum Failure
> Reporter: Etienne Dube
>
> Hi, not sure if it is the right place to report this problem but I haven't found anywhere else.
> Some md5 and sha1 hash files don't have the right format in http://repo1.maven.org/maven2/commons-pool/commons-pool/1.3/
> The culprits are commons-pool-1.3-sources.jar.md5 and commons-pool-1.3-sources.jar.sha1. For example:
> SHA1(commons-pool-1.3-sources.jar)= 97f4c4b0144792c8173199cec14c3948c91aff81
> The leading "SHA1(commons-pool-1.3-sources.jar)= " string causes mvn or ivy to fail with an "invalid sha1" error when downloading commons-pool-1.3-sources.jar
> Thanks
--
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: (MEV-628) bad md5 / sha1 files in commons-pool-1.3
Posted by "Benjamin Bentmann (JIRA)" <ji...@codehaus.org>.
[ http://jira.codehaus.org/browse/MEV-628?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Benjamin Bentmann closed MEV-628.
---------------------------------
Assignee: Benjamin Bentmann
Resolution: Not A Bug
> bad md5 / sha1 files in commons-pool-1.3
> ----------------------------------------
>
> Key: MEV-628
> URL: http://jira.codehaus.org/browse/MEV-628
> Project: Maven Evangelism
> Issue Type: Bug
> Components: Checksum Failure
> Reporter: Etienne Dube
> Assignee: Benjamin Bentmann
>
> Hi, not sure if it is the right place to report this problem but I haven't found anywhere else.
> Some md5 and sha1 hash files don't have the right format in http://repo1.maven.org/maven2/commons-pool/commons-pool/1.3/
> The culprits are commons-pool-1.3-sources.jar.md5 and commons-pool-1.3-sources.jar.sha1. For example:
> SHA1(commons-pool-1.3-sources.jar)= 97f4c4b0144792c8173199cec14c3948c91aff81
> The leading "SHA1(commons-pool-1.3-sources.jar)= " string causes mvn or ivy to fail with an "invalid sha1" error when downloading commons-pool-1.3-sources.jar
> Thanks
--
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] Moved: (MEV-628) bad md5 / sha1 files in commons-pool-1.3
Posted by "Benjamin Bentmann (JIRA)" <ji...@codehaus.org>.
[ http://jira.codehaus.org/browse/MEV-628?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Benjamin Bentmann moved MAVENUPLOAD-2513 to MEV-628:
----------------------------------------------------
Group ID: commons-pool
Bundle URL: (was: http://repo1.maven.org/maven2/commons-pool/commons-pool/1.3/)
Artifact ID: commons-pool
Version: 1.3
Workflow: jira (was: Maven New)
Key: MEV-628 (was: MAVENUPLOAD-2513)
Project: Maven Evangelism (was: Maven Upload Requests)
> bad md5 / sha1 files in commons-pool-1.3
> ----------------------------------------
>
> Key: MEV-628
> URL: http://jira.codehaus.org/browse/MEV-628
> Project: Maven Evangelism
> Issue Type: Bug
> Components: Checksum Failure
> Reporter: Etienne Dube
>
> Hi, not sure if it is the right place to report this problem but I haven't found anywhere else.
> Some md5 and sha1 hash files don't have the right format in http://repo1.maven.org/maven2/commons-pool/commons-pool/1.3/
> The culprits are commons-pool-1.3-sources.jar.md5 and commons-pool-1.3-sources.jar.sha1. For example:
> SHA1(commons-pool-1.3-sources.jar)= 97f4c4b0144792c8173199cec14c3948c91aff81
> The leading "SHA1(commons-pool-1.3-sources.jar)= " string causes mvn or ivy to fail with an "invalid sha1" error when downloading commons-pool-1.3-sources.jar
> Thanks
--
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: (MEV-628) bad md5 / sha1 files in
commons-pool-1.3
Posted by "Benjamin Bentmann (JIRA)" <ji...@codehaus.org>.
[ http://jira.codehaus.org/browse/MEV-628?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=183308#action_183308 ]
Benjamin Bentmann commented on MEV-628:
---------------------------------------
This is fixed in recent Maven versions as per MNG-1349.
> bad md5 / sha1 files in commons-pool-1.3
> ----------------------------------------
>
> Key: MEV-628
> URL: http://jira.codehaus.org/browse/MEV-628
> Project: Maven Evangelism
> Issue Type: Bug
> Components: Checksum Failure
> Reporter: Etienne Dube
>
> Hi, not sure if it is the right place to report this problem but I haven't found anywhere else.
> Some md5 and sha1 hash files don't have the right format in http://repo1.maven.org/maven2/commons-pool/commons-pool/1.3/
> The culprits are commons-pool-1.3-sources.jar.md5 and commons-pool-1.3-sources.jar.sha1. For example:
> SHA1(commons-pool-1.3-sources.jar)= 97f4c4b0144792c8173199cec14c3948c91aff81
> The leading "SHA1(commons-pool-1.3-sources.jar)= " string causes mvn or ivy to fail with an "invalid sha1" error when downloading commons-pool-1.3-sources.jar
> Thanks
--
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