RE: Maven 3.0 Deployment Problem

[Harper, Brad]

Thanks to the reply from Ryan Connolly [which unfortunately isn't
reflected here].

 

Indeed, maven 3.x doesn't support the ssh file transport by default and
I needed to add a build extension for the correct wagon artifact

 

    <extensions>

      <extension>

        <groupId>org.apache.maven.wagon</groupId>

        <artifactId>wagon-ssh</artifactId>

        <version>1.0-beta-6</version>

      </extension>

    </extensions>

 

I had reviewed the maven 3.x compatibility notes at

 

  https://cwiki.apache.org/MAVEN/maven-3x-compatibility-notes.html

 

but it didn't register with that our builds would be affected by this
change.

 

I am a little uneasy, however, using a 'beta' version of the artifact.
Beta-6 seems to be the latest/best available. Is this the case?

 

Thanks for the help.

 

Brad

 

From: Harper, Brad 
Sent: Friday, October 29, 2010 5:22 PM
To: users@maven.apache.org
Subject: Maven 3.0 Deployment Problem

 

I just switched [from Maven 2.2.1] to give 3.0 a try and ran into a
problem during deployment. The crux of the output seems to be

 

   No implementation for org.apache.maven.wagon.Wagon annotated with
@Named(value=scp) was bound

 

Nothing obvious jumps out in a web search containing key parts of this
text.

 

I'm not explicitly managing or configuring the deploy plugin. Any ideas?
Thanks.

 

Brad