maven-cargo

I'm using the Cargo Maven plugin to deploy a WAR to a remote server, and I'm having problems. I'll probably create a second question for that problem, but this one is about overriding a Maven plugin's log4j configuration. Cargo uses JBoss' client libraries to ship stuff to JBoss servers (which I'm trying to do.) The JBoss library uses log4j. Cargo doesn't set up any sort of mapping layer that I know of. So, essentially, log messages are occurring in the dependent library of a Maven plugin. I tried setting -Dlog4j.debug and got this information: log4j: Trying to find [log4j.xml] using

I would like to distribute my application packaged as WAR embedded in Apache Tomcat. That is I want to distribute Tomcat along with my application. How can this sort of distribution packaging can be done with Maven? I have seen the Maven Cargo Plugin , but it appears to be geared towards deploying applications in containers locally. Perhaps an additional step over Cargo plugin is what I need. cargo:package appears to be interesting but lacks documentation. Elaborating Tomasz's comment, you can do the following to achieve this. Download and install tomcat to your local repository. mvn install

I am trying to deploy remotely a WAR file to JBoss 5.0.1 GA using Cargo maven plugin but it seems that I can't. I have found similar threads but none of them finally helped me to solve my problem. I follow these instructions . Some points that seem to be important are: As of CARGO 1.0.3, the way CARGO supports remote deployments on the JBoss Application Server has drastically evolved. Starting from JBoss 5.x, JBoss has a Deployment Manager that can be used for deploying things on the JBoss server. My pom file looks like this: <plugin> <groupId>org.codehaus.cargo</groupId> <artifactId>cargo

I'd like to keep Tomcat's context.xml file out of my WAR file's META-INF directory if possible. Can this be done with Maven's cargo plugin? I can't seem to find the correct configuration. Eureka! After many days of studying this problem I finally found a very effective solution. The key is to take your Tomcat XML context fragment file and use the <configfiles> element of cargo to drop it in the conf/Catalina/localhost directory with the name context.xml.default . The only downside is that this will make your context definitions available to all web-apps, but this shouldn't really matter only