Fhomasp wrote:
Hey,
Thanks for your replies.
The thing with the older commons-logging implementations is because of
dependencies, configured through maven2, on older programming logic.
Because of these dependencies there's at least two versions of commons
logging in my classpath.
)
at
org.mortbay.jetty.webapp.TagLibConfiguration.configureWebApp(TagLibConfiguration.java:239
)
I'm at a loss on how to get this issue fixed. If anyone knows what to
do,
by all means let me know ;-)
--
View this message in context:
http://www.nabble.com/cargo-maven2-plugin-causing-exceptions-during-build-because
-causing-exceptions-during-build-because-of-commons-logging-tp19197018p19197018.html
Sent from the Commons - Issues mailing list archive at Nabble.com.
The simplest thing to do is to put a commons-logging.properties into the
classpath. The file should contain just one property to set the logging
implementation to something other than log4j, like this:
org.apache.commons.logging.Log=org.apache.commons.logging.impl.SimpleLog
Fhomasp wrote:
Hey,
Yes, hopefully Dennis' suggestion will work.
It does look like whatever environment this code is running in, it is
using a rather old version of commons-logging. The reported exception
only occurs in commons-logging 1.0.x. Version 1.1 of commons-logging was
released in May 2006 and 1.1.1 was
