[
http://jira.codehaus.org/browse/MSITE-379?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=162446#action_162446
]
Dennis Lundberg commented on MSITE-379:
---------------------------------------
This sounds a lot like MSITE-211 that was fixed in 2.0-beta-7.
Can you provide us with an example pom.xml to go with the settings.xml bits you
showed above?
> 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: http://jira.codehaus.org/browse/MSITE-379
> Project: Maven 2.x 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
>
> 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>
--
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
