ant-notifications mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Matthias Bläsing (JIRA) <j...@apache.org>
Subject [jira] [Updated] (IVY-1031) Support for Web Proxy exclusions
Date Wed, 06 Jul 2011 11:00:16 GMT

     [ https://issues.apache.org/jira/browse/IVY-1031?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]

Matthias Bläsing updated IVY-1031:
----------------------------------

    Attachment: httpclient-useproxyselector.patch

Attached you find a potential fix I use for our internal system. It patches ivy, so that it
uses the java proxy selector (since 1.5), that decides which proxy to use.

I had to remove the caching, as the selector might report a different proxy for each url.
But as an ant script is normaly not performance critical I consider this a solution.

The patch needs to be reworked, please be free to comment and I'll try to rework it.

> Support for Web Proxy exclusions
> --------------------------------
>
>                 Key: IVY-1031
>                 URL: https://issues.apache.org/jira/browse/IVY-1031
>             Project: Ivy
>          Issue Type: New Feature
>          Components: Core
>    Affects Versions: 2.0
>         Environment: N/A
>            Reporter: Adam krieg
>            Priority: Minor
>         Attachments: httpclient-useproxyselector.patch
>
>
> In my corporate environment, we have our own repository with most of our artifacts. 
However there are some artifacts we retrieve from external sources.  To access those sources,
we need to go through a web proxy.  However if we set the web proxy settings, we are unable
to resolve the internal artifacts.
> It would be nice to have Ivy be able to use the proxy for certain domains (or all domains
by default) with an exclusion, like *.mycompany.com.  Eclipse does something similar to this.

--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira

       

Mime
View raw message