[
https://jira.codehaus.org/browse/MNG-202?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=354014#comment-354014
]
Edwin Wiles commented on MNG-202:
---------------------------------
I work with a team that has contractors from two companies on it. Between
those people, we have the following situations:
# Company A's network, with company A's Proxy, and company A's Nexus mirror.
# Company B's network, ditto.
# Company A's VPN, with a different Proxy, and maybe access to the mirror.
# Company B's VPN, ditto.
# Home Network with Proxy
## ...without Mirror.
## ...with Mirror
# Home Network without Proxy
## ...without Mirror.
## ...with Mirror.
This is a mobile workforce, any of these people can be in pretty much any of
these situations. A single source for all of them (a Proxy PAC) file, would go
a LONG way to reducing the problem.
And before you can say "well if you have a mirror, you don't need the proxy",
don't ever think that. There are still things that get done inside the Maven
Java instance that require Proxy access that doesn't go through the mirror.
I tried putting the proxies and/or mirrors into properties in profiles, and
having the proxy and mirror setup done via those properties. It didn't work at
all.
I've actually filed another ticket, one asking for both Proxies and Mirrors to
be added to the list of things you can put inside Profiles. In some respects,
that would be an even better solution, but the PAC solution appeared to have
some code already associated with it, and was therefore more likely to be
implemented sooner.
Even if we get the Proxies and Mirrors inside Profiles, the ability to use the
PAC files would still be useful. That way, when corporate network management
makes a change to the proxies, we'd pick it up automatically.
> Add support of .pac file for proxy configuration
> ------------------------------------------------
>
> Key: MNG-202
> URL: https://jira.codehaus.org/browse/MNG-202
> Project: Maven
> Issue Type: New Feature
> Components: Artifacts and Repositories
> Reporter: Emmanuel Venisse
> Priority: Minor
>
> Authorize Proxy Auto-Config File (.pac file) for proxy configuration in user
> model.
> http://wp.netscape.com/eng/mozilla/2.0/relnotes/demo/proxy-live.html
> =>Use rhino for read the pac file.
--
This message was sent by Atlassian JIRA
(v6.1.6#6162)
