You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@maven.apache.org by "David Hook (JIRA)" <ji...@codehaus.org> on 2010/11/15 04:48:03 UTC
[jira] Created: (MAVENUPLOAD-2808) Bouncy Castle checksums cause
failure in Maven 3.0, please re-sync checksums
Bouncy Castle checksums cause failure in Maven 3.0, please re-sync checksums
----------------------------------------------------------------------------
Key: MAVENUPLOAD-2808
URL: http://jira.codehaus.org/browse/MAVENUPLOAD-2808
Project: Maven Upload Requests
Issue Type: Task
Reporter: David Hook
The BC checksums were originally in the form
hash filename
It turns out that Maven 3.0 cannot cope with this.
(See http://www.bouncycastle.org/jira/browse/BJA-298)
I have fixed the checksum files in the official BC sync area, but need someone to clear them from the repository so they get uploaded again.
Thanks,
David
--
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: (MAVENUPLOAD-2808) Bouncy Castle checksums cause
failure in Maven 3.0, please re-sync checksums
Posted by "Juven Xu (JIRA)" <ji...@codehaus.org>.
[ http://jira.codehaus.org/browse/MAVENUPLOAD-2808?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Juven Xu closed MAVENUPLOAD-2808.
---------------------------------
Resolution: Fixed
Assignee: Juven Xu
fixed, correct checksum will be in central in 1 hour
> Bouncy Castle checksums cause failure in Maven 3.0, please re-sync checksums
> ----------------------------------------------------------------------------
>
> Key: MAVENUPLOAD-2808
> URL: http://jira.codehaus.org/browse/MAVENUPLOAD-2808
> Project: Maven Upload Requests
> Issue Type: Task
> Reporter: David Hook
> Assignee: Juven Xu
>
> The BC checksums were originally in the form
> hash filename
> It turns out that Maven 3.0 cannot cope with this.
> (See http://www.bouncycastle.org/jira/browse/BJA-298)
> I have fixed the checksum files in the official BC sync area, but need someone to clear them from the repository so they get uploaded again.
> Thanks,
> David
--
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: (MAVENUPLOAD-2808) Bouncy Castle checksums cause
failure in Maven 3.0, please re-sync checksums
Posted by "Juven Xu (JIRA)" <ji...@codehaus.org>.
[ http://jira.codehaus.org/browse/MAVENUPLOAD-2808?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=251423#action_251423 ]
Juven Xu commented on MAVENUPLOAD-2808:
---------------------------------------
this MAVENUPLOAD project will be closed soon, please go to https://issues.sonatype.org/browse/MVNCENTRAL if you have any other problem
and this issue is cloned to https://issues.sonatype.org/browse/MVNCENTRAL-32
> Bouncy Castle checksums cause failure in Maven 3.0, please re-sync checksums
> ----------------------------------------------------------------------------
>
> Key: MAVENUPLOAD-2808
> URL: http://jira.codehaus.org/browse/MAVENUPLOAD-2808
> Project: Maven Upload Requests
> Issue Type: Task
> Reporter: David Hook
> Assignee: Juven Xu
>
> The BC checksums were originally in the form
> hash filename
> It turns out that Maven 3.0 cannot cope with this.
> (See http://www.bouncycastle.org/jira/browse/BJA-298)
> I have fixed the checksum files in the official BC sync area, but need someone to clear them from the repository so they get uploaded again.
> Thanks,
> David
--
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