maven-cargo

问题 I am trying to run embedded Tomcat 9 inside Maven 3 for integration testing purposes. I was led to cargo-maven2-plugin by other SO answers. So, attempting to follow the instructions found here: https://codehaus-cargo.github.io/cargo/Static+deployment+of+WAR.html I have this fragment in a simple POM: <build> <plugins> <plugin> <groupId>org.codehaus.cargo</groupId> <artifactId>cargo-maven2-plugin</artifactId> <version>1.7.6</version> <configuration> <container> <containerId>tomcat9x<

问题 I am trying to run embedded Tomcat 9 inside Maven 3 for integration testing purposes. I was led to cargo-maven2-plugin by other SO answers. So, attempting to follow the instructions found here: https://codehaus-cargo.github.io/cargo/Static+deployment+of+WAR.html I have this fragment in a simple POM: <build> <plugins> <plugin> <groupId>org.codehaus.cargo</groupId> <artifactId>cargo-maven2-plugin</artifactId> <version>1.7.6</version> <configuration> <container> <containerId>tomcat9x<

问题 I am trying to run embedded Tomcat 9 inside Maven 3 for integration testing purposes. I was led to cargo-maven2-plugin by other SO answers. So, attempting to follow the instructions found here: https://codehaus-cargo.github.io/cargo/Static+deployment+of+WAR.html I have this fragment in a simple POM: <build> <plugins> <plugin> <groupId>org.codehaus.cargo</groupId> <artifactId>cargo-maven2-plugin</artifactId> <version>1.7.6</version> <configuration> <container> <containerId>tomcat9x<

问题 I am trying to implement the solution mentioned in How to specify jetty-env.xml file for Maven Cargo plugin for Jetty? However I am facing something even more fundamental: My Cargo is simply not generating any context xml. <plugin> <groupId>org.codehaus.cargo</groupId> <artifactId>cargo-maven2-plugin</artifactId> <version>1.2.1</version> <configuration> <!-- Container configuration --> <container> <containerId>jetty6x</containerId> <type>embedded</type> </container> <!-- Configuration to use

问题 I'm using Maven 3.0.3. Is there a way I can use the Maven Cargo plugin to spin up an embedded Tomcat server? Right now, it seems I have to install it myself first. I get this error when I try and change the container type to "embedded" ... [ERROR] Failed to execute goal org.codehaus.cargo:cargo-maven2-plugin:1.1.2:run (default-cli) on project jx: Execution default-cli of goal org.codehaus.cargo:cargo-maven2-plugin:1.1.2:run failed: Cannot create configuration. There's no registered

问题 I have a developed application and I am just trying to make the build process easy. The POM file for parent looks like this: <parent> <groupId>com.shc.obu.ca</groupId> <artifactId>shcobuca-pom</artifactId> <version>1.1.0</version> </parent> <groupId>com.shc.obu.ca.osol</groupId> <artifactId>apps-pom</artifactId> <version>${currVersion}</version> <packaging>pom</packaging> <name>Outlet Apps</name> <scm> <connection>scm:svn:https://ushofsvpsvn2.intra.searshc.com/svn/outlet/outlet/trunk/apps<

问题 I want cargo maven plugin to start a Tomcat7 so i put into my pom: <plugin> <groupId>org.codehaus.cargo</groupId> <artifactId>cargo-maven2-plugin</artifactId> <version>1.2.0</version> <!-- minimal configuration to let adb run (mvn package org.codehaus.cargo:cargo-maven2-plugin:run) in a local tomcat --> <configuration> <containerId>tomcat7x</containerId> <containerUrl>http://archive.apache.org/dist/tomcat/tomcat-7/v7.0.16/bin/apache-tomcat-7.0.16.zip </containerUrl> <configuration>

问题 I have a maven project which extends an existing parent project (It's the "standard product" from which my product will be a "Customized product"). The parent declares a org.codehaus.cargo / cargo-maven2-plugin and passes it some VM args under configuration / cargo.jvmargs . Like this: <plugin> <groupId>org.codehaus.cargo</groupId> <artifactId>cargo-maven2-plugin</artifactId> <version>1.4.18</version> <configuration> <container> <containerId>tomcat8x</containerId> [...] <dependencies> [...] <

问题 I am migrating from Maven's jetty plugin to the Cargo plugin (cargo-maven2-plugin) because Cargo will happily run WARs from dependent Maven modules. Within out web-app we have taken great pains to externalize all configuration through JNDI. These JNDI definitions are web-app specific and therefore are placed in a jetty-env.xml file that is outside the WAR. Using the Jetty plugin, we specified this file as follows: <plugin> <groupId>org.mortbay.jetty</groupId> <artifactId>maven-jetty-plugin<

问题 Has someone successfully deployed EAR remotely to JBoss 5.1.0.GA? My pom.xml configuration is as follows: <plugin> <groupId>org.codehaus.cargo</groupId> <artifactId>cargo-maven2-plugin</artifactId> <version>1.0.1-SNAPSHOT</version> <configuration> <container> <containerId>jboss51x</containerId> <type>remote</type> <timeout>600000</timeout> </container> <configuration> <type>runtime</type> <properties> <cargo.remote.username>username</cargo.remote.username> <cargo.remote.password>password<