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: http://blogs.exist.com/bporter/2008/02/25/working-around-non-interactive-problems-in-leopards-subversion/
> My other option and my prefered option is to
> submit a patch that gets rolled into the nightly build of the wagon
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.