[jira] Commented: (MCHANGES-60) The jira report should handle the nonProxyHosts specified in settings.xml

["Marcus Schulte (JIRA)" <ji...@codehaus.org>]

    [ http://jira.codehaus.org/browse/MCHANGES-60?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_105391 ] 

Marcus Schulte commented on MCHANGES-60:
----------------------------------------

Separator character should be the pipe (|). Wildcards should be supported. See http://maven.apache.org/guides/mini/guide-proxies.html .

This Bug (yes it *is* a bug ;) ) renders the plugin unusable for us, because our proxy refuses to proxy internal servers.

> The jira report should handle the nonProxyHosts specified in settings.xml
> -------------------------------------------------------------------------
>
>                 Key: MCHANGES-60
>                 URL: http://jira.codehaus.org/browse/MCHANGES-60
>             Project: Maven 2.x Changes Plugin
>          Issue Type: Improvement
>          Components: jira-report
>    Affects Versions: 2.0-beta-2
>         Environment: A network with a proxy to access the outside, and a JIRA inside the network.
>            Reporter: Pierre-Antoine Grégoire
>
> These nonProxyHosts can be retrieved with the settings.getActiveProxy().getNonProxyHosts();
> This returns a String containing a (usually?)comma-separated list of nonProxyHosts.
> If the jira URL matches one of these hosts, it should not use any proxy of course ;).
> I haven't found a nonProxyHosts concept in commons-httpclient, so it should be checked in the determineProxy Method of AbstractJiraDownloader.
> This is quickly fixed and would be very useful ;)
> Thanks in advance

-- 
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