[ https://jira.codehaus.org/browse/WAGON-346?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
nicolas de loof closed WAGON-346. --------------------------------- Resolution: Fixed Fix Version/s: 2.0 1.x Fixed in 1.x using a class level synchronized block > 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.x, 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. For more information on JIRA, see: http://www.atlassian.com/software/jira