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.
25 10:06:08.484::INFO: Extract
>> > jar:file:/C:/projects/trunk/vlafo/olympus/JSFUnitTest/target
>> > /JSFUnitTestWar-1.4.2.war!/ to C:\DOCUME~1\DEVELO~
>> >
>> 1\LOCALS~1\Temp\Jetty_0_0_0_0_8080_JSFUnitTestWar-1.4.2.war__JSFUnitTestWar-1_4_2__aar4a7\webapp
>> > 2008-08-25 10:06:12.781::WARN: failed
>> > [EMAIL
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 relea
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,
exceptions-during-build-because-of-commons-logging-tp19197018p19197018.html
Sent from the Commons - Issues mailing list archive at Nabble.com.
