Hello,
I am trying to migrate from maven 2.2.1 to maven 3.0.4. My configuration
involves a private ssh/scp server acting both as a repository and a
pluginRepository. The problem is that maven 3 cannot recognize the
pluginRepository properly, it fails with the following combination of
warning and errors:
[WARNING] Could not transfer metadata my-group/maven-metadata.xml
from/to myrepop (scpexe://myhost): No connector available to access
repository altsolp (scpexe://myhost) of type default using the available
factories WagonRepositoryConnectorFactory
[ERROR] No plugin found for prefix 'myrepop' in the current project and
in the plugin groups [my-group, org.apache.maven.plugins,
org.codehaus.mojo] available from the repositories [local
(~/.m2/repository), myrepop (scpexe://myhost), central
(http://repo.maven.apache.org/maven2)]
I also tried using the fullpath:
mvn my-group:my-plugin:my-version:myTarget
Then the warning doesn't show up, just the following error (which is the
same problem description in other words):
[ERROR] Plugin my-group:my-plugin:my-version or one of its dependencies
could not be resolved: Failed to read artifact descriptor for
my-group:my-plugin:my-version: Could not transfer artifact
my-group:my-plugin:my-version from/to myrepop (scpexe://myhost): No
connector available to access repository myrepop (scpexe://myhost) of
type default using the available factories
WagonRepositoryConnectorFactory -> [Help 1]
It seems impossible to convince Maven 3 to operate the pluginRepository
server using wagon-ssh-external. If I switch it to http://, it works
like a charm, but I prefer to access it using ssh.
Using scpexe://myhost as a maven repo works ok for Maven 3. Maven 2 also
works with the same configuration for both repo and pluginRepo.
Does anyone have a clue ? Is it somehow possible to use ssh
pluginRepositories ?
Thanks in advance for your help.
My settings.xml includes:
<pluginGroups>
<pluginGroup>my.package</pluginGroup>
</pluginGroups>
<servers>
<server>
<id>myrepo</id>
<username>me</username>
<configuration>
<sshExecutable>ssh</sshExecutable>
<scpExecutable>scp</scpExecutable>
</configuration>
</server>
<server>
<id>myrepop</id>
<username>me</username>
<configuration>
<sshExecutable>ssh</sshExecutable>
<scpExecutable>scp</scpExecutable>
</configuration>
</server>
</servers>
....
<repositories>
<repository>
<id>myrepo</id>
<name>myrepo</name>
<url>scpexe://myhost</url>
</repository>
</repositories>
<pluginRepositories>
<pluginRepository>
<name>myrepop</name>
<id>myrepop</id>
<url>scpexe://myhost</url>
</pluginRepository>
</pluginRepositories>
My project's pom.xml includes:
<build>
<extensions>
<extension>
<groupId>org.apache.maven.wagon</groupId>
<artifactId>wagon-ssh-external</artifactId>
<version>2.2</version> <!-- also tried
with 1.0-beta-6 -->
</extension>
</extensions>
<plugins>
<plugin>
<groupId>my.package</groupId>
<artifactId>my-plugin</artifactId>
<version>my-version</version>
....
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
For additional commands, e-mail: users-help@maven.apache.org
the default wagons in Maven 3.0 were trimmed. you will need to add the appropriate wagon as a build extension On 13 July 2012 17:11, Thanos Kyritsis <dj...@linux.gr> wrote: > Hello, > > I am trying to migrate from maven 2.2.1 to maven 3.0.4. My configuration > involves a private ssh/scp server acting both as a repository and a > pluginRepository. The problem is that maven 3 cannot recognize the > pluginRepository properly, it fails with the following combination of > warning and errors: > > [WARNING] Could not transfer metadata my-group/maven-metadata.xml from/to > myrepop (scpexe://myhost): No connector available to access repository > altsolp (scpexe://myhost) of type default using the available factories > WagonRepositoryConnectorFactor**y > > [ERROR] No plugin found for prefix 'myrepop' in the current project and in > the plugin groups [my-group, org.apache.maven.plugins, org.codehaus.mojo] > available from the repositories [local (~/.m2/repository), myrepop > (scpexe://myhost), central (http://repo.maven.apache.org/**maven2<http://repo.maven.apache.org/maven2> > )] > > I also tried using the fullpath: > mvn my-group:my-plugin:my-version:**myTarget > > Then the warning doesn't show up, just the following error (which is the > same problem description in other words): > > [ERROR] Plugin my-group:my-plugin:my-version or one of its dependencies > could not be resolved: Failed to read artifact descriptor for > my-group:my-plugin:my-version: Could not transfer artifact > my-group:my-plugin:my-version from/to myrepop (scpexe://myhost): No > connector available to access repository myrepop (scpexe://myhost) of type > default using the available factories WagonRepositoryConnectorFactor**y > -> [Help 1] > > It seems impossible to convince Maven 3 to operate the pluginRepository > server using wagon-ssh-external. If I switch it to http://, it works like > a charm, but I prefer to access it using ssh. > > Using scpexe://myhost as a maven repo works ok for Maven 3. Maven 2 also > works with the same configuration for both repo and pluginRepo. > > Does anyone have a clue ? Is it somehow possible to use ssh > pluginRepositories ? > Thanks in advance for your help. > > > My settings.xml includes: > > <pluginGroups> > <pluginGroup>my.package</**pluginGroup> > </pluginGroups> > > <servers> > <server> > <id>myrepo</id> > <username>me</username> > <configuration> > <sshExecutable>ssh</**sshExecutable> > <scpExecutable>scp</**scpExecutable> > </configuration> > </server> > <server> > <id>myrepop</id> > <username>me</username> > <configuration> > <sshExecutable>ssh</**sshExecutable> > <scpExecutable>scp</**scpExecutable> > </configuration> > </server> > </servers> > > .... > > <repositories> > <repository> > <id>myrepo</id> > <name>myrepo</name> > <url>scpexe://myhost</url> > </repository> > </repositories> > > <pluginRepositories> > <pluginRepository> > <name>myrepop</name> > <id>myrepop</id> > <url>scpexe://myhost</url> > </pluginRepository> > </pluginRepositories> > > > My project's pom.xml includes: > > > <build> > <extensions> > <extension> > <groupId>org.apache.maven.**wagon</groupId> > <artifactId>wagon-ssh-**external</artifactId> > <version>2.2</version> <!-- also tried > with 1.0-beta-6 --> > </extension> > </extensions> > > <plugins> > <plugin> > <groupId>my.package</groupId> > <artifactId>my-plugin</**artifactId> > <version>my-version</version> > .... > > > ------------------------------**------------------------------**--------- > To unsubscribe, e-mail: users-unsubscribe@maven.**apache.org<us...@maven.apache.org> > For additional commands, e-mail: users-help@maven.apache.org > >
https://github.com/jvanzyl/maven-recipes/tree/master/deploy-with-scp-extension On Jul 13, 2012, at 12:11 PM, Thanos Kyritsis wrote: > Hello, > > I am trying to migrate from maven 2.2.1 to maven 3.0.4. My configuration involves a private ssh/scp server acting both as a repository and a pluginRepository. The problem is that maven 3 cannot recognize the pluginRepository properly, it fails with the following combination of warning and errors: > > [WARNING] Could not transfer metadata my-group/maven-metadata.xml from/to myrepop (scpexe://myhost): No connector available to access repository altsolp (scpexe://myhost) of type default using the available factories WagonRepositoryConnectorFactory > > [ERROR] No plugin found for prefix 'myrepop' in the current project and in the plugin groups [my-group, org.apache.maven.plugins, org.codehaus.mojo] available from the repositories [local (~/.m2/repository), myrepop (scpexe://myhost), central (http://repo.maven.apache.org/maven2)] > > I also tried using the fullpath: > mvn my-group:my-plugin:my-version:myTarget > > Then the warning doesn't show up, just the following error (which is the same problem description in other words): > > [ERROR] Plugin my-group:my-plugin:my-version or one of its dependencies could not be resolved: Failed to read artifact descriptor for my-group:my-plugin:my-version: Could not transfer artifact my-group:my-plugin:my-version from/to myrepop (scpexe://myhost): No connector available to access repository myrepop (scpexe://myhost) of type default using the available factories WagonRepositoryConnectorFactory -> [Help 1] > > It seems impossible to convince Maven 3 to operate the pluginRepository server using wagon-ssh-external. If I switch it to http://, it works like a charm, but I prefer to access it using ssh. > > Using scpexe://myhost as a maven repo works ok for Maven 3. Maven 2 also works with the same configuration for both repo and pluginRepo. > > Does anyone have a clue ? Is it somehow possible to use ssh pluginRepositories ? > Thanks in advance for your help. > > > My settings.xml includes: > > <pluginGroups> > <pluginGroup>my.package</pluginGroup> > </pluginGroups> > > <servers> > <server> > <id>myrepo</id> > <username>me</username> > <configuration> > <sshExecutable>ssh</sshExecutable> > <scpExecutable>scp</scpExecutable> > </configuration> > </server> > <server> > <id>myrepop</id> > <username>me</username> > <configuration> > <sshExecutable>ssh</sshExecutable> > <scpExecutable>scp</scpExecutable> > </configuration> > </server> > </servers> > > .... > > <repositories> > <repository> > <id>myrepo</id> > <name>myrepo</name> > <url>scpexe://myhost</url> > </repository> > </repositories> > > <pluginRepositories> > <pluginRepository> > <name>myrepop</name> > <id>myrepop</id> > <url>scpexe://myhost</url> > </pluginRepository> > </pluginRepositories> > > > My project's pom.xml includes: > > > <build> > <extensions> > <extension> > <groupId>org.apache.maven.wagon</groupId> > <artifactId>wagon-ssh-external</artifactId> > <version>2.2</version> <!-- also tried with 1.0-beta-6 --> > </extension> > </extensions> > > <plugins> > <plugin> > <groupId>my.package</groupId> > <artifactId>my-plugin</artifactId> > <version>my-version</version> > .... > > > --------------------------------------------------------------------- > To unsubscribe, e-mail: users-unsubscribe@maven.apache.org > For additional commands, e-mail: users-help@maven.apache.org > Thanks, Jason ---------------------------------------------------------- Jason van Zyl Founder & CTO, Sonatype Founder, Apache Maven http://twitter.com/jvanzyl --------------------------------------------------------- First, the taking in of scattered particulars under one Idea, so that everyone understands what is being talked about ... Second, the separation of the Idea into parts, by dividing it at the joints, as nature directs, not breaking any limb in half as a bad carver might. -- Plato, Phaedrus (Notes on the Synthesis of Form by C. Alexander)