You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@maven.apache.org by "Robert Scholte (JIRA)" <ji...@codehaus.org> on 2014/06/17 21:34:10 UTC
[jira] (MSITE-379) The SCP commands in site use a proxy if an HTTP
proxy is defined, but doesn't abide to the nonProxyHosts.
[ https://jira.codehaus.org/browse/MSITE-379?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Robert Scholte updated MSITE-379:
---------------------------------
Description:
I setup an HTTP proxy in my settings.xml and it breaks the site:deploy plugin which is set to SCP to an internal server. This is due to the wagon-ssh using the HTTP proxy settings but not abiding to the nonProxyHosts. If I add the following to my settings.xml, my build works again:
{code:xml}
<proxies>
<proxy>
<id>espn.proxy</id>
<protocol>http</protocol>
<host>examplehttpproxy.espn3.com</host>
<port>8080</port>
<nonProxyHosts>*.espn3.com</nonProxyHosts>
</proxy>
<!-- This is needed because the wagon-ssh thinks it uses a proxy if the HTTP one above is defined, and yet it doesn't use the nonProxyHosts above, instead it needs the one below -->
<proxy>
<id>espn.proxy.scp</id>
<protocol>scp</protocol>
<host>dummy</host>
<port>1234</port>
<nonProxyHosts>*.espn3.com</nonProxyHosts>
</proxy>
</proxies>
{code:xml}
was:
I setup an HTTP proxy in my settings.xml and it breaks the site:deploy plugin which is set to SCP to an internal server. This is due to the wagon-ssh using the HTTP proxy settings but not abiding to the nonProxyHosts. If I add the following to my settings.xml, my build works again:
<proxies>
<proxy>
<id>espn.proxy</id>
<protocol>http</protocol>
<host>examplehttpproxy.espn3.com</host>
<port>8080</port>
<nonProxyHosts>*.espn3.com</nonProxyHosts>
</proxy>
<!-- This is needed because the wagon-ssh thinks it uses a proxy if the HTTP one above is defined, and yet it doesn't use the nonProxyHosts above, instead it needs the one below -->
<proxy>
<id>espn.proxy.scp</id>
<protocol>scp</protocol>
<host>dummy</host>
<port>1234</port>
<nonProxyHosts>*.espn3.com</nonProxyHosts>
</proxy>
</proxies>
> The SCP commands in site use a proxy if an HTTP proxy is defined, but doesn't abide to the nonProxyHosts.
> ---------------------------------------------------------------------------------------------------------
>
> Key: MSITE-379
> URL: https://jira.codehaus.org/browse/MSITE-379
> Project: Maven Site Plugin
> Issue Type: Bug
> Components: site:deploy
> Affects Versions: 2.0-beta-7
> Environment: Mac OS X 10.5, Maven 2.0.8
> Reporter: Brian Jackson
> Attachments: pom copy.xml
>
>
> I setup an HTTP proxy in my settings.xml and it breaks the site:deploy plugin which is set to SCP to an internal server. This is due to the wagon-ssh using the HTTP proxy settings but not abiding to the nonProxyHosts. If I add the following to my settings.xml, my build works again:
> {code:xml}
> <proxies>
> <proxy>
> <id>espn.proxy</id>
> <protocol>http</protocol>
> <host>examplehttpproxy.espn3.com</host>
> <port>8080</port>
> <nonProxyHosts>*.espn3.com</nonProxyHosts>
> </proxy>
> <!-- This is needed because the wagon-ssh thinks it uses a proxy if the HTTP one above is defined, and yet it doesn't use the nonProxyHosts above, instead it needs the one below -->
> <proxy>
> <id>espn.proxy.scp</id>
> <protocol>scp</protocol>
> <host>dummy</host>
> <port>1234</port>
> <nonProxyHosts>*.espn3.com</nonProxyHosts>
> </proxy>
> </proxies>
> {code:xml}
--
This message was sent by Atlassian JIRA
(v6.1.6#6162)