[
https://jira.codehaus.org/browse/MNG-202?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=354019#comment-354019
]
Michael Osipov commented on MNG-202:
------------------------------------
Proxies and mirrors won't get into profiles that fast because that would
require a model change. Not possible before Maven 4. Regarding the PAC, I do
understand your pain. We do you PACs too but luckily, I am happy with just the
proxy name.
Using the PAC file depends on the Wagon transport used for HTTP. See
[here|http://maven.apache.org/wagon/]. One can pass custom attributes to a
transport in the {{settings.xml}} without changing the model. So the options
are improve the lightweight transport or create a JIRA issue with Apache HTTP
Client for PAC Proxy support and provide a fix. Then this can be used with
Maven.
What do you think? If this sounds reasonable, I would move this issue to Wagon.
> 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)
