The solution to my problem with jetty6 and cargo-maven2-plugin was to
add the following systemProperties element to the container
configuration to the jetty6 container's configuration element:
container
containerIdjetty6x/containerId
Hi Dennis,
Thank you for your helpful note. I tried specifying the property to turn
on common-logging 1.1 diags using all of the following but did not get
any output:
* mvn -Dorg.apache.commons.logging.diagnostics.dest=STDOUT cargo:start
* env
Hello,
I am using cargo-maven2-plugin for deploying my webapp into my webcontainer.
I have no problems using tomcat5x profile but when I use the jetty6x
profile with:
container
containerIdjetty6x/containerId
This is a classic, but really has nothing to do with Maven.
The root cause is that commons-logging and log4j are in different class
loaders. The best way to track down what is going on is to install
commons-logging 1.1 (if you are not already using that version) and to
turn on diagnostics
