maven-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Timothy Riley (JIRA)" <>
Subject [jira] Commented: (WAGON-258) SSH / SCP -o options should be quoted
Date Wed, 15 Apr 2009 04:44:12 GMT


Timothy Riley commented on WAGON-258:

Brett Porter 
Has suggested the following workarounds...

One quick workaround might be to put an intervening script in between  
maven and the PATH that corrects the problem, something like:

> My other option and my prefered option is to
> submit a patch that gets rolled into the nightly build of the wagon
> provider.

This would be best - certainly submit the issue and patch to be rolled  
in. Adding the quotes is not harmful to openssh, so I'd say it's ok to  
add them for all cases.

I wouldn't recommend using a snapshot though - instead it's best if  
you release the library internally (1.0-beta-5-MYCOMPANY-1) and use  
that. This assumes you've set up your own repository and the builds  
all use it.

Adding the following will then override the Maven one:

Once the Wagon is formally released you can replace the version with  
the new one.


> SSH / SCP -o options should be quoted
> -------------------------------------
>                 Key: WAGON-258
>                 URL:
>             Project: Maven Wagon
>          Issue Type: Bug
>          Components: wagon-ssh-external
>    Affects Versions: 1.0-beta-5
>         Environment: Maven 2.1.0 and Java 1.5.0_15
>            Reporter: Timothy Riley
> I'm currently using Reflection Secure IT, which requires all SSH / SCP -o options
> be placed in quotations unfortunately I cannot deviate from this technology.
> The problem is that places the BatchMode option as an
> argument without quotes resulting in a failing SSH command.
> Line 251 of
>    cl.createArgument().setValue( "BatchMode yes" );
> Results in...
> ssh -o BatchMode yes [REST OF COMMAND]
> What I need is...
> ssh -o "BatchMode yes" [REST OF COMMAND]

This message is automatically generated by JIRA.
If you think it was sent incorrectly contact one of the administrators:
For more information on JIRA, see:


View raw message