[
http://jira.codehaus.org/browse/MNG-2066?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=218537#action_218537
]
Barrie Treloar commented on MNG-2066:
-------------------------------------
As Jason says in the comment above:
If you are using nexus then it is nexus that does all the internet
communication (and therefore doesn't suffer this problem)
For all your maven repository needs your internal machines talk to nexus only.
You will only need a proxy for non-maven repository things, like javadoc link
aggregation.
> Specify multiple proxies
> ------------------------
>
> Key: MNG-2066
> URL: http://jira.codehaus.org/browse/MNG-2066
> Project: Maven 2 & 3
> Issue Type: Improvement
> Affects Versions: 2.0.2
> Reporter: Thomas Recloux
> Attachments: MNG-2066-maven-site.patch, MNG-2066-maven.patch,
> multiple-proxies-paches.zip
>
>
> After this discussion :
> http://www.mail-archive.com/d...@maven.apache.org/msg53099.html
> In the attached zip file, you'll find four patch files :
> - on the maven-artifact-manager projet : changes in the DefaultWagonManager
> class, using the http proxy when no https proxy is specified.
> - on the maven-core project : changes in the DefaultMaven, adding all teh
> active proxies from the settings to the wagon manager
> - on the maven-settings project : changes in the settings.mdo file
> Theses patches are built on the maven-2.0.x branch.
--
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
