[jira] (WAGON-346) LightWeight http wagon not thread-safe

["nicolas de loof (JIRA)" <ji...@codehaus.org>]

    [ https://jira.codehaus.org/browse/WAGON-346?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=292730#comment-292730 ] 

nicolas de loof commented on WAGON-346:
---------------------------------------

@Mark you're right, so the only way to get this fixed is to deprecate wagon-http-lightweight and definitively remove it from wagon project as URLConnection can't be used in a concurrent context
                
> LightWeight http wagon not thread-safe
> --------------------------------------
>
>                 Key: WAGON-346
>                 URL: https://jira.codehaus.org/browse/WAGON-346
>             Project: Maven Wagon
>          Issue Type: Bug
>          Components: wagon-http-lightweight
>    Affects Versions: 1.0
>         Environment: maven 3 with Aether
>            Reporter: nicolas de loof
>             Fix For: 1.1, 2.0
>
>
> Aether (maven3) by default parallelized metadata resolution on 4 threads (aether.metadataResolver.threads) and artifacts downloading on 5 (maven.artifact.threads).
> In such context, Wagon is not used sequentially.
> LightWeightHttpWagon is designed for mono-thread, sequential usage. It rely on system properties and on setting/resetting java.net.Authenticator singleton. 
> The result is that, in some cases (typically : when settings defines many repositories with various credentials), credentials may not apply and download will fail
> A potential fix is 
> - to use Java5 URL.openConnection(Proxy) instead of using system properties
> - to use a shared, singleton java.net.Authenticator that lookup repositories to match the requested URL

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://jira.codehaus.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira