You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@maven.apache.org by "Mark Struberg (JIRA)" <ji...@codehaus.org> on 2011/08/22 22:29:32 UTC
[jira] Commented: (WAGON-346) LightWeight http wagon not
thread-safe
[ https://jira.codehaus.org/browse/WAGON-346?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=276717#comment-276717 ]
Mark Struberg commented on WAGON-346:
-------------------------------------
+1 for using URL.openConnection(Proxy)
wagon-2.0 (current trunk) got upgraded to java5 already. So all necessary requirements should be met.
> 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
>
> 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.
For more information on JIRA, see: http://www.atlassian.com/software/jira