[ 
https://issues.apache.org/jira/browse/COMPRESS-104?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Sebb resolved COMPRESS-104.
---------------------------

    Resolution: Fixed

Reported on d...@maven, and the problem has been fixed.

> The SHA1 files uploaded to the maven repository are not formatted correctly, 
> and make it impossible to use Commons-Compress with maven or ivy
> ---------------------------------------------------------------------------------------------------------------------------------------------
>
>                 Key: COMPRESS-104
>                 URL: https://issues.apache.org/jira/browse/COMPRESS-104
>             Project: Commons Compress
>          Issue Type: Bug
>    Affects Versions: 1.0
>         Environment: maven 2.0
> ivy 2.1.0
>            Reporter: Kevin Squire
>             Fix For: 1.0
>
>   Original Estimate: 0.5h
>  Remaining Estimate: 0.5h
>
> In the maven repository at 
> http://repo1.maven.org/maven2/org/apache/commons/commons-compress/1.0/ (and 
> mirrors), the SHA1 file for each uploaded file looks like this (shown is 
> commons-compress-1.0.pom.sha1):
> commons-compress-1.0.pom: 3259 80A0 9DBB D0C1 08EC  E8E7 733B 462B 00E6 F2A8
> This file is in the wrong format for maven and ivy to parse, causing them not 
> to be able to download and use commons-compress.
> The file should contain only the sha1 hash, with no spaces, as
> 325980a09dbbd0c108ece8e7733b462b00e6f2a8
> Please fix the sha1 key for all files and re-upload.  
> (For reference, see: 
> http://maven.apache.org/guides/mini/guide-central-repository-upload.html)
> See corresponding maven upload bug report at 
> http://jira.codehaus.org/browse/MAVENUPLOAD-2756

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.

Reply via email to