You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@maven.apache.org by "Michael Osipov (JIRA)" <ji...@codehaus.org> on 2014/12/22 17:39:10 UTC

[jira] (WAGON-428) site:deploy ignores .ssh/config details and throws exception/error

     [ https://jira.codehaus.org/browse/WAGON-428?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Michael Osipov moved MSITE-673 to WAGON-428:
--------------------------------------------

          Component/s:     (was: site:deploy)
                       wagon-ssh
    Affects Version/s:     (was: 3.0)
                       2.8
           Issue Type: Improvement  (was: Bug)
                  Key: WAGON-428  (was: MSITE-673)
              Project: Maven Wagon  (was: Maven Site Plugin)

> site:deploy ignores .ssh/config details and throws exception/error
> ------------------------------------------------------------------
>
>                 Key: WAGON-428
>                 URL: https://jira.codehaus.org/browse/WAGON-428
>             Project: Maven Wagon
>          Issue Type: Improvement
>          Components: wagon-ssh
>    Affects Versions: 2.8
>            Reporter: Fred Cooke
>
> This is certainly not an issue with m-site-p, however it may well not be an issue in wagon-provider-api either, as it's on 2.2 and site is still using 1.0.
> I have my site distribution URL configured like so:
> {{ <url>scp://private-site/home/private/site/releases/${project.groupId}/${project.artifactId}/${project.version}/</url> }}
> Where "private-site" is an ssh configuration like this output from cat ~/.ssh/config:
> {noformat}
> Host private-site
> 	Hostname real.domain.name
> 	Port 1234
> {noformat}
> However site:deploy (presumably using wagon) ignores this and throws the following:
> {noformat}
> [ERROR] Failed to execute goal org.apache.maven.plugins:maven-site-plugin:3.0:deploy (default-cli) on project myProject: Error uploading site: Cannot connect. Reason: java.net.UnknownHostException: private-site -> [Help 1]
> {noformat}
> I believe this is still an issue with site 3.2, however will check upon request.



--
This message was sent by Atlassian JIRA
(v6.1.6#6162)