You are viewing a plain text version of this content. The canonical link for it is here.
Posted to users@maven.apache.org by Marcel May <ma...@consol.de> on 2007/02/15 17:59:38 UTC

maven 2.0.5, site-deploy and ssh (jsch) proxy problem?

Hi!

While trying to update mvn from 2.0.4 to 2.0.5 I discovered that
"site-deploy" fails with a proxy error message although scp is used (see
below).
The site-deploy stuff worked perfectly for my project with the old mvn
2.0.4.

settings.xml:
    ...
      <proxy>
      <id>my-proxy</id>
      <active>true</active>
      <protocol>http</protocol>
      <host>proxy</host>
      <port>8001</port>
    </proxy>
  ...
  <servers>
    <server>
      <id>my-site</id>
      <username>mm</username>
      <password>XXX</password>
    </server>
  </servers>


pom.xml:
  <distributionManagement>
    <site>
      <id>my-site</id>
      <url>scp://site-server/home/mm/www/htdocs/</url>
    </site>
  </distributionManagement>


There is a proxy configured in the settings.xml, but that should be of
no concern for scp, right?
It seems that the Wagon provider updates in mvn 2.0.5 will automatically
use SSH via proxy, if there is an active proxy in settings.xml.


The output is:
...[
INFO] [site:deploy]
scp://site-server/home/mm/www/htdocs - Session: Disconnecting
scp://site-server/home/mm/www/htdocs - Session: Disconnected
[INFO]
------------------------------------------------------------------------
[ERROR] BUILD ERROR
[INFO]
------------------------------------------------------------------------
[INFO] Error uploading site

Embedded error: Cannot connect. Reason: ProxyHTTP: java.io.IOException:
proxy error: Forbidden
[INFO]
------------------------------------------------------------------------
[DEBUG] Trace
org.apache.maven.lifecycle.LifecycleExecutionException: Error uploading site
    at
org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoals(DefaultLifecycleExecutor.java:564)
    at
org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoalWithLifecycle(DefaultLifecycleExecutor.java:480)
    at
org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoal(DefaultLifecycleExecutor.java:459)
    at
org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoalAndHandleFailures(DefaultLifecycleExecutor.java:311)
    at
org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeTaskSegments(DefaultLifecycleExecutor.java:278)
    at
org.apache.maven.lifecycle.DefaultLifecycleExecutor.execute(DefaultLifecycleExecutor.java:143)
    at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:330)
    at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:123)
    at org.apache.maven.cli.MavenCli.main(MavenCli.java:272)
    at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
    at
sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
    at
sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
    at java.lang.reflect.Method.invoke(Method.java:585)
    at org.codehaus.classworlds.Launcher.launchEnhanced(Launcher.java:315)
    at org.codehaus.classworlds.Launcher.launch(Launcher.java:255)
    at org.codehaus.classworlds.Launcher.mainWithExitCode(Launcher.java:430)
    at org.codehaus.classworlds.Launcher.main(Launcher.java:375)
Caused by: org.apache.maven.plugin.MojoExecutionException: Error
uploading site
    at
org.apache.maven.plugins.site.SiteDeployMojo.execute(SiteDeployMojo.java:184)
    at
org.apache.maven.plugin.DefaultPluginManager.executeMojo(DefaultPluginManager.java:420)
    at
org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoals(DefaultLifecycleExecutor.java:539)
    ... 16 more
Caused by:
org.apache.maven.wagon.authentication.AuthenticationException: Cannot
connect. Reason: ProxyHTTP: java.io.IOException: proxy error: Forbidden
    at
org.apache.maven.wagon.providers.ssh.jsch.AbstractJschWagon.openConnection(AbstractJschWagon.java:186)
    at org.apache.maven.wagon.AbstractWagon.connect(AbstractWagon.java:143)
    at
org.apache.maven.plugins.site.SiteDeployMojo.execute(SiteDeployMojo.java:149)
    ... 18 more
Caused by: com.jcraft.jsch.JSchException: ProxyHTTP:
java.io.IOException: proxy error: Forbidden
    at com.jcraft.jsch.ProxyHTTP.connect(Unknown Source)
    at com.jcraft.jsch.Session.connect(Unknown Source)
    at com.jcraft.jsch.Session.connect(Unknown Source)
    at
org.apache.maven.wagon.providers.ssh.jsch.AbstractJschWagon.openConnection(AbstractJschWagon.java:158)
    ... 20 more
[INFO]
------------------------------------------------------------------------
[INFO] Total time: 49 seconds
[INFO] Finished at: Thu Feb 15 12:13:02 CET 2007
[INFO] Final Memory: 43M/80M
[INFO]
------------------------------------------------------------------------
>

Maven site plugin version is 2.0-beta-5. The proxy configured in
settings.xml does not have any authentication configured.

Is there any way to turn off the proxy usage for site-deploy if there is
an active proxy in settings.xml?
Should I rise a feature request for the maven-site-plugin?

Thanks alot,
Marcel


---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
For additional commands, e-mail: users-help@maven.apache.org


Re: maven 2.0.5, site-deploy and ssh (jsch) proxy problem?

Posted by Antonio Parolini <An...@hcuge.ch>.
We have the same with maven 2.0.6. MAven is using the proxy setting for other
protocols than HTTP. As a workaround, we stick to 2.0.4.

-toni


Marcel May-2 wrote:
> 
> Hi!
> 
> While trying to update mvn from 2.0.4 to 2.0.5 I discovered that
> "site-deploy" fails with a proxy error message although scp is used (see
> below).
> The site-deploy stuff worked perfectly for my project with the old mvn
> 2.0.4.
> 
> settings.xml:
>     ...
>       <proxy>
>       <id>my-proxy</id>
>       <active>true</active>
>       <protocol>http</protocol>
>       <host>proxy</host>
>       <port>8001</port>
>     </proxy>
>   ...
>   <servers>
>     <server>
>       <id>my-site</id>
>       <username>mm</username>
>       <password>XXX</password>
>     </server>
>   </servers>
> 
> 
> pom.xml:
>   <distributionManagement>
>     <site>
>       <id>my-site</id>
>       <url>scp://site-server/home/mm/www/htdocs/</url>
>     </site>
>   </distributionManagement>
> 
> 
> There is a proxy configured in the settings.xml, but that should be of
> no concern for scp, right?
> It seems that the Wagon provider updates in mvn 2.0.5 will automatically
> use SSH via proxy, if there is an active proxy in settings.xml.
> 
> 
> The output is:
> ...[
> INFO] [site:deploy]
> scp://site-server/home/mm/www/htdocs - Session: Disconnecting
> scp://site-server/home/mm/www/htdocs - Session: Disconnected
> [INFO]
> ------------------------------------------------------------------------
> [ERROR] BUILD ERROR
> [INFO]
> ------------------------------------------------------------------------
> [INFO] Error uploading site
> 
> Embedded error: Cannot connect. Reason: ProxyHTTP: java.io.IOException:
> proxy error: Forbidden
> [INFO]
> ------------------------------------------------------------------------
> [DEBUG] Trace
> org.apache.maven.lifecycle.LifecycleExecutionException: Error uploading
> site
>     at
> org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoals(DefaultLifecycleExecutor.java:564)
>     at
> org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoalWithLifecycle(DefaultLifecycleExecutor.java:480)
>     at
> org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoal(DefaultLifecycleExecutor.java:459)
>     at
> org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoalAndHandleFailures(DefaultLifecycleExecutor.java:311)
>     at
> org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeTaskSegments(DefaultLifecycleExecutor.java:278)
>     at
> org.apache.maven.lifecycle.DefaultLifecycleExecutor.execute(DefaultLifecycleExecutor.java:143)
>     at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:330)
>     at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:123)
>     at org.apache.maven.cli.MavenCli.main(MavenCli.java:272)
>     at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
>     at
> sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
>     at
> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
>     at java.lang.reflect.Method.invoke(Method.java:585)
>     at org.codehaus.classworlds.Launcher.launchEnhanced(Launcher.java:315)
>     at org.codehaus.classworlds.Launcher.launch(Launcher.java:255)
>     at
> org.codehaus.classworlds.Launcher.mainWithExitCode(Launcher.java:430)
>     at org.codehaus.classworlds.Launcher.main(Launcher.java:375)
> Caused by: org.apache.maven.plugin.MojoExecutionException: Error
> uploading site
>     at
> org.apache.maven.plugins.site.SiteDeployMojo.execute(SiteDeployMojo.java:184)
>     at
> org.apache.maven.plugin.DefaultPluginManager.executeMojo(DefaultPluginManager.java:420)
>     at
> org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoals(DefaultLifecycleExecutor.java:539)
>     ... 16 more
> Caused by:
> org.apache.maven.wagon.authentication.AuthenticationException: Cannot
> connect. Reason: ProxyHTTP: java.io.IOException: proxy error: Forbidden
>     at
> org.apache.maven.wagon.providers.ssh.jsch.AbstractJschWagon.openConnection(AbstractJschWagon.java:186)
>     at
> org.apache.maven.wagon.AbstractWagon.connect(AbstractWagon.java:143)
>     at
> org.apache.maven.plugins.site.SiteDeployMojo.execute(SiteDeployMojo.java:149)
>     ... 18 more
> Caused by: com.jcraft.jsch.JSchException: ProxyHTTP:
> java.io.IOException: proxy error: Forbidden
>     at com.jcraft.jsch.ProxyHTTP.connect(Unknown Source)
>     at com.jcraft.jsch.Session.connect(Unknown Source)
>     at com.jcraft.jsch.Session.connect(Unknown Source)
>     at
> org.apache.maven.wagon.providers.ssh.jsch.AbstractJschWagon.openConnection(AbstractJschWagon.java:158)
>     ... 20 more
> [INFO]
> ------------------------------------------------------------------------
> [INFO] Total time: 49 seconds
> [INFO] Finished at: Thu Feb 15 12:13:02 CET 2007
> [INFO] Final Memory: 43M/80M
> [INFO]
> ------------------------------------------------------------------------
>>
> 
> Maven site plugin version is 2.0-beta-5. The proxy configured in
> settings.xml does not have any authentication configured.
> 
> Is there any way to turn off the proxy usage for site-deploy if there is
> an active proxy in settings.xml?
> Should I rise a feature request for the maven-site-plugin?
> 
> Thanks alot,
> Marcel
> 
> 
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
> For additional commands, e-mail: users-help@maven.apache.org
> 
> 
> 

-- 
View this message in context: http://www.nabble.com/maven-2.0.5%2C-site-deploy-and-ssh-%28jsch%29-proxy-problem--tf3235028s177.html#a10177521
Sent from the Maven - Users mailing list archive at Nabble.com.


---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
For additional commands, e-mail: users-help@maven.apache.org