You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@maven.apache.org by "Andy Geach (JIRA)" <ji...@codehaus.org> on 2008/08/19 09:39:26 UTC

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

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

Andy Geach updated MCHANGES-60:
-------------------------------

    Attachment: MNG-MCHANGES-60-MCHANGES-123-maven-changes-plugin.patch

This patch fixes the issue - if JIRA is hosted on a non-proxy host as specified in settings.xml, then the request is not routed via the proxy. The helper method that matches the JIRA host with non-proxy hosts is copied from org.apache.maven.wagon.proxy.ProxyUtils (which is in project wagon-provider-api version 1.0-beta-4). In the future, when maven-changes-plugin updates its dependency on maven-project to a more recent version, then the method can be removed.

Note that this patch also fixes issue MCHANGES-123

> 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
>         Attachments: MNG-MCHANGES-60-MCHANGES-123-maven-changes-plugin.patch
>
>
> 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