On 14/04/2009, at 11:30 AM, Tim Riley wrote:
I have run into a situation with the wagon-ssh-external version 1.0-
beta-5
and maven 2.1.0. Before I attempt to fix the problem myself I wanted
to ask
here if there is another solution.
I'm currently using Reflection Secure IT, which requires all SSH -o
options
be placed in quotations unfortunately I cannot deviate from this
technology.
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
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:
<build>
<extensions>
<extension>
<groupId>org.apache.maven.wagon</groupId>
<artifactId>wagon-ssh-external</artifactId>
<version>1.0-beta-5-MYCOMPANY-1</version>
</extension>
</extensions>
</build>
Once the Wagon is formally released you can replace the version with
the new one.
Cheers,
Brett
---------------------------------------------------------------------
To unsubscribe, e-mail: wagon-users-unsubscr...@maven.apache.org
For additional commands, e-mail: wagon-users-h...@maven.apache.org
