[jira] [Comment Edited] (MNG-5559) upgrade to last wagon 2.6

["Wolfgang Fahl (JIRA)" <ji...@apache.org>]

    [ https://issues.apache.org/jira/browse/MNG-5559?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14519587#comment-14519587 ] 

Wolfgang Fahl edited comment on MNG-5559 at 4/29/15 3:41 PM:
-------------------------------------------------------------

Just had the same symptoms as this issue with mvn 3.3.1 on Mac OS 10.9.5 using macports. Downgrading to 3.0.5 fixed it.
The issue had been Discussed with Robert Scholte for a few month but there has been no resolution as of today.  The main problem is the hangup with no further message and no timeout.

The first question would be how to debug this situation and get a
log file of what actually happens. Please note that the output of
the command line maven shows 718/717 Bytes ... (or the like) when it
hangs while in eclipse you only get "updating maven project 25%" ...
when it hangs.
The command line maven can be stopped with CTRL-C while the eclipse
process can only be forced to be killed  which is the really bad
thing.
It seems that there is not even a timeout configured. So the main issue
for me would be:

 1. How to debug
 2. add a time out
 3. add an option to esc/break within eclipse
 4. fix the issue 


was (Author: wolfgangfahl):
Just had the same symptoms as this issue with mvn 3.3.1 on Mac OS 10.9.5 using macports. Downgrading to 3.0.5 fixed it.
The issue had been Discussed with Robert Scholten for a few month but there has been no resolution as of today.  The main problem is the hangup with no further message and no timeout.

The first question would be how to debug this situation and get a
log file of what actually happens. Please note that the output of
the command line maven shows 718/717 Bytes ... (or the like) when it
hangs while in eclipse you only get "updating maven project 25%" ...
when it hangs.
The command line maven can be stopped with CTRL-C while the eclipse
process can only be forced to be killed  which is the really bad
thing.
It seems that there is not even a timeout configured. So the main issue
for me would be:

 1. How to debug
 2. add a time out
 3. add an option to esc/break within eclipse
 4. fix the issue 

> upgrade to last wagon 2.6
> -------------------------
>
>                 Key: MNG-5559
>                 URL: https://issues.apache.org/jira/browse/MNG-5559
>             Project: Maven
>          Issue Type: Bug
>          Components: Dependencies
>            Reporter: Olivier Lamy (*$^¨%`£)
>            Assignee: Olivier Lamy (*$^¨%`£)
>             Fix For: 3.2.1
>
>
> Release Notes - Maven Wagon - Version 2.5
> ** Bug
>     * [WAGON-381] - Both Maven 2 and 3 fail to retrieve a <dependency> that is larger than Integer.MAX_VALUE
>     * [WAGON-384] - Maven fails to download artifacts larger than 2 GB
>     * [WAGON-394] - upgrade commons-logging to 1.1.2
>     * [WAGON-395] - intermittent "ProtocolException: The server failed to respond with a valid HTTP response"
>     * [WAGON-399] - Fix for SFTP on windows machine
> ** Improvement
>     * [WAGON-388] - remove wagon-http-shared4 dependency on httpclient
> Release Notes - Maven Wagon - Version 2.6
> ** Improvement
>     * [WAGON-401] - Access Denied due to missing User-Agent
>     * [WAGON-402] - Upgrade Apache HttpClient based wagon provider to HttpClient 4.3
>     * [WAGON-403] - SSH agent support for wagon-ssh



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)