David Blacka wrote:
> Harrie Hazewinkel wrote:
>
>> HI,
>>
>> While checking out the functionality of beepcore-java
>> I run into a problem of the API with log4j. Attached is a
>> patch that fixes the code for a recent 1.3 version of log4j.
>> Hope it will be applied.
>
>
> What was the actual problem?
>
> I will note that the commons-logging package will absolutely use log4j
> if log4j is present in the classpath. You should be able to configure
> log4j first, and control the behavior of the commons-logging package. At
> that point, it is just a basic wrapper around log4j.
>
While compiling the code I got a lot of errors, like package not found
(due to classpatch indeed), but also some method API problems.
While investigating I saw you seemed to have a different API
for it (the common-logging), so I changed it directly into a recent
version of the log4j.
I did not follow log4j that close, but if I understand it well
it as become a more 'stand-alone' package with the name log4j.
The logging-common is still there, but would you really keep that
layer in between? You may decide that.
cheers,
Harrie
|
