[
https://jira.codehaus.org/browse/MSITE-673?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=316424#comment-316424
]
Fred Cooke commented on MSITE-673:
----------------------------------
Definitely still an issue with 3.2. After working around MSITE-600 and friends
I'm not back to here. I fooled it by adding "private-site" to my /etc/hosts
file, however the port is wrong, so connection refused. I can't change the port
of my server (obviously) and I don't want something so specific in the pom file
when I may have to change it in future. I want the details externalised. I
guess I have to work around this too by including the port in the url
somewhere. No, the work around is to use scpexe: and the external ssh extension.
{{
<extension>
<groupId>org.apache.maven.wagon</groupId>
<artifactId>wagon-ssh-external</artifactId>
<version>${extension.version.wagon}</version>
</extension>
}}
Out of all of today's workarounds and issues, this one is the least bad. I
don't like it, and native support should be present, but this works, for me,
for now, on this box, though likely not on winblows.
> site:deploy ignores .ssh/config details and throws exception/error
> ------------------------------------------------------------------
>
> Key: MSITE-673
> URL: https://jira.codehaus.org/browse/MSITE-673
> Project: Maven 2.x and 3.x Site Plugin
> Issue Type: Bug
> Components: site:deploy
> Affects Versions: 3.0
> 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 is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://jira.codehaus.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
