[
http://jira.codehaus.org/browse/MNG-2066?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jason van Zyl updated MNG-2066:
-------------------------------
Priority: (was: Major)
This is too complicated for Maven. If you have more then one repository that
you need to use then you can use one of the many proxying tools. Trying to
cycle through proxies doesn't seem all that great. And really you want to be
able to bind a proxy to a particular repository as you know what you are trying
to get and where. This is not the right solution. Nothing more then simple
proxy support belongs in Maven as the proxying solutions are available now and
work. See Proximity.
> Specify multiple proxies
> ------------------------
>
> Key: MNG-2066
> URL: http://jira.codehaus.org/browse/MNG-2066
> Project: Maven 2
> Issue Type: Improvement
> Affects Versions: 2.0.2
> Reporter: Thomas Recloux
> Fix For: 2.1.x
>
> Attachments: MNG-2066-maven-site.patch, MNG-2066-maven.patch,
> multiple-proxies-paches.zip
>
>
> After this discussion :
> http://www.mail-archive.com/[EMAIL PROTECTED]/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
