|
View:
New views
3 Messages
—
Rating Filter:
Alert me
|
|
|
No plugin found for prefix 'cargo'Hi all,
I am new to maven and after some tests I decided to give a try on cargo. I found some tutorials on the internet, did the required changes to my pom and tried to deploy an EAR to JBoss. Strangely, everytime I call mvn install cargo:deploy (through m2Eclipse) it fails with the error message of no plugin found for prefix 'cargo'. The odd thing is that I can see in the build process that it tries to lookup the maven-metadata.xml from http://repository.codehaus.org/org/codehaus/mojo/maven-metadata.xml instead of http://repository.codehaus.org/org/codehaus/cargo/mojo/maven-metadata.xml and in fact the first one does not declare a cargo prefix. I've declared the plugin repository as follows: <pluginRepositories> <pluginRepository> <id>codehaus snapshot repository</id> <url>http://repository.codehaus.org</url> <releases> <enabled>true</enabled> </releases> </pluginRepository> </pluginRepositories> And the plugin configuration: <build> <pluginManagement> <plugins> <plugin> <groupId>org.codehaus.cargo</groupId> <artifactId>cargo-maven2-plugin</artifactId> <version>1.0.1-SNAPSHOT</version> <configuration> <wait>false</wait> <container> <containerid>jboss4x</containerid> <type>remote</type> </container> <type>runtime</type> <home>/software/jboss-4.2.3.GA/server/default</home> </configuration> </plugin> </plugins> </pluginManagement> </build> Am I doing something wrong? What is making maven look for the cargo maven-metadata.xml on wrong url? best regards, Rafael Ribeiro |
|
|
Re: No plugin found for prefix 'cargo'Hi Rafael,
I don't think you can deploy to JBoss remotely. This has been a known issue for some time. Someone correct me if I am wrong. I am using cargo to deploy to local JBoss all the time. Here is how I configured it. You can set a property in the pom.xml as <properties> <jboss.hom>/your/path/to/jboss</jboss.home> </properties> I use the initialize phase for *other* reasons, but you should probably bake it into the package phase instead. <plugin> <!-- This will deploy to local JBOSS if you run mvn initialize cargo:deploy cargo:start. Then you can hit the URL http://localhost:8080 --> <groupId>org.codehaus.cargo</groupId> <artifactId>cargo-maven2-plugin</artifactId> <version>1.0</version> <executions> <execution> <phase>initialize</phase> </execution> </executions> <configuration> <wait>true</wait> <container> <containerId>jboss42x</containerId> <home>${jboss.home}</home> </container> <configuration> <type>existing</type> <home>${jboss.home}/server/default</home> </configuration> </configuration> </plugin> I have the following pluginRepositories defined: <pluginRepositories> <pluginRepository> <id>codehaus</id> <name>Codehaus Release Repo</name> <url>http://repository.codehaus.org</url> </pluginRepository> <pluginRepository> <id>codehaus-snapshot</id> <name>Codehaus Snapshot Repo</name> <url>http://snapshots.repository.codehaus.org</url> </pluginRepository> </pluginRepositories> On Tue, Aug 11, 2009 at 7:58 AM, Rafael Ribeiro<rafaelri@...> wrote: > > Hi all, > > I am new to maven and after some tests I decided to give a try on cargo. I > found some tutorials on the internet, did the required changes to my pom and > tried to deploy an EAR to JBoss. > Strangely, everytime I call mvn install cargo:deploy (through m2Eclipse) it > fails with the error message of no plugin found for prefix 'cargo'. The odd > thing is that I can see in the build process that it tries to lookup the > maven-metadata.xml from > http://repository.codehaus.org/org/codehaus/mojo/maven-metadata.xml instead > of http://repository.codehaus.org/org/codehaus/cargo/mojo/maven-metadata.xml > and in fact the first one does not declare a cargo prefix. > I've declared the plugin repository as follows: > <pluginRepositories> > <pluginRepository> > <id>codehaus snapshot repository</id> > <url>http://repository.codehaus.org</url> > <releases> > <enabled>true</enabled> > </releases> > </pluginRepository> > </pluginRepositories> > > And the plugin configuration: > > <build> > <pluginManagement> > <plugins> > <plugin> > <groupId>org.codehaus.cargo</groupId> > <artifactId>cargo-maven2-plugin</artifactId> > <version>1.0.1-SNAPSHOT</version> > <configuration> > <wait>false</wait> > <container> > <containerid>jboss4x</containerid> > <type>remote</type> > </container> > <type>runtime</type> > <home>/software/jboss-4.2.3.GA/server/default</home> > </configuration> > </plugin> > </plugins> > </pluginManagement> > </build> > > Am I doing something wrong? What is making maven look for the cargo > maven-metadata.xml on wrong url? > > best regards, > Rafael Ribeiro > -- > View this message in context: http://www.nabble.com/No-plugin-found-for-prefix-%27cargo%27-tp24916194p24916194.html > Sent from the Cargo - User mailing list archive at Nabble.com. > > > --------------------------------------------------------------------- > To unsubscribe from this list, please visit: > > http://xircles.codehaus.org/manage_email > > > -- Zeno Consulting, Inc. home: http://www.zenoconsulting.biz blog: http://zenoconsulting.wikidot.com p: 248.894.4922 f: 313.884.2977 --------------------------------------------------------------------- To unsubscribe from this list, please visit: http://xircles.codehaus.org/manage_email |
|
|
Re: No plugin found for prefix 'cargo'Hi Davis!
I managed to get it working, first of all the plugin cannot be placed under pluginManagement it has to be deployed under build->plugins->plugin <build> <plugins> <plugin> <groupId>org.codehaus.cargo</groupId> <artifactId>cargo-maven2-plugin</artifactId> <configuration> <wait>false</wait> <container> <containerId>jboss4x</containerId> <type>remote</type> </container> <type>runtime</type> <home>/software/jboss-4.2.3.GA/server/default</home> </configuration> </plugin> </plugins> and configured the repository as follows: <repositories> <repository> <id>codehaus</id> <name>codehaus</name> <url>http://snapshots.repository.codehaus.org</url> </repository> Sincerely as I am really new to maven and cargo I wont risk saying it is doing remotely but at least it is working ;) Tks for the help! regards, Rafael Ribeiro
|
| Free embeddable forum powered by Nabble | Forum Help |