[
http://jira.codehaus.org/browse/WAGON-308?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=266064#action_266064
]
Jan Sievers commented on WAGON-308:
-----------------------------------
The only workaround we found is to use the commons http wagon implementation
<build>
<extensions>
<extension>
<groupId>org.apache.maven.wagon</groupId>
<artifactId>wagon-http</artifactId>
<version>1.0-beta-7</version>
</extension>
</extensions>
</build>
We also tried reducing the number of threads used to 1 uisng
"-Daether.connector.wagon.threads=1" but this did not help.
This problem appears globally for us and changing all poms/parent poms to use a
different wagon is not feasible.
Do you have other options for workarounds?
Thanks
Jan
> Use of proxy properties in lightweight http wagon is not thread-safe
> --------------------------------------------------------------------
>
> Key: WAGON-308
> URL: http://jira.codehaus.org/browse/WAGON-308
> Project: Maven Wagon
> Issue Type: Bug
> Components: wagon-http-lightweight
> Affects Versions: 1.0-beta-6
> Reporter: Benjamin Bentmann
>
> The usage of system properties to configure the proxy for the lightweight
> wagon makes it not thread safe. E.g. as discovered by the Maven IT for
> MNG-2305, this concurrency issue makes parallel artifact resolution via proxy
> fail intermittently.
> Moving on to Java 1.5+ APIs, it should be feasible to fix this via
> per-connection proxy settings.
--
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
