Created: (MNG-4235) [regression] Maven 2.2.0 produces invalid checksums

[regression] Maven 2.2.0 produces invalid checksums
---------------------------------------------------

                 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




--
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

       

     [ http://jira.codehaus.org/browse/MNG-4235?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

John Casey updated MNG-4235:
----------------------------

    Fix Version/s: 2.2.1

> [regression] Maven 2.2.0 produces invalid checksums
> ---------------------------------------------------
>
>                 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

       

    [ http://jira.codehaus.org/browse/MNG-4235?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=183160#action_183160 ]

Kenneth Flynn commented on MNG-4235:
------------------------------------

I am definitely seeing this for all our Maven projects.  Had to revert to an earlier version to avoid this.  I can provide more details if required/reproduction.

> [regression] Maven 2.2.0 produces invalid checksums
> ---------------------------------------------------
>
>                 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

       

     [ http://jira.codehaus.org/browse/MNG-4235?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Benjamin Bentmann updated MNG-4235:
-----------------------------------

    Summary: [regression] Maven 2.2.0 produces invalid checksums during deployment to secured HTTP repo  (was: [regression] Maven 2.2.0 produces invalid checksums)

> [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

       

    [ 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

       

     [ http://jira.codehaus.org/browse/MNG-4235?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

John Casey closed MNG-4235.
---------------------------

      Assignee: John Casey
    Resolution: Fixed

Reverting to use of lightweight-http wagon by default, while still enabling the use of the httpclient-driven wagon if properly configured. We're tracking the long-term solution to the problem in the httpclient-driven wagon in WAGON-277.

> [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
>            Assignee: 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