You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@maven.apache.org by "John Casey (JIRA)" <ji...@codehaus.org> on 2009/07/14 01:41:22 UTC
[jira] Commented: (MNG-4235) [regression] Maven 2.2.0 produces
invalid checksums during deployment to secured HTTP repo
[ http://jira.codehaus.org/browse/MNG-4235?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=183452#action_183452 ]
John Casey commented on MNG-4235:
---------------------------------
This *SHOULD* mean that the checksum error should happen also for the very first file transferred for any given deployment in a Maven 2.1.0 environment. It seems that the Sun implementation sends the first transfer twice, then caches authentication and uses it for preemptive authentication in subsequent transfers.
We should check this out under the above circumstances.
> [regression] Maven 2.2.0 produces invalid checksums during deployment to secured HTTP repo
> ------------------------------------------------------------------------------------------
>
> Key: MNG-4235
> URL: http://jira.codehaus.org/browse/MNG-4235
> Project: Maven 2
> Issue Type: Bug
> Components: Artifacts and Repositories
> Affects Versions: 2.2.0
> Reporter: John Casey
> Priority: Blocker
> Fix For: 2.2.1
>
>
--
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