cocoon-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Torsten Curdt" <tcu...@apache.org>
Subject Re: Re: Logging in 2.2
Date Thu, 24 Aug 2006 04:26:16 GMT
<snip/>

> But in this case Cocoon would end up with two log files - one is regular
> core.log (created, say, by good old LogKit) and another one from the log4j from
> 'new code'...

agree - ugly!

> I'd prefer commons-logging over log4j for reasons:
>
>   * it supports all of them - LogKit, Java logging, log4j;
>   * it seems to be already used in many (most?) libraries throughout Apache;
>
>
> That is assuming that any class loading issues can be resolved.

The latest release should have fixed most issues. Drop a mail to Simon
on commons-dev he would be the one that knows the details. FYI the JCL
plan is to make "fancy" discovery mechansim completely optional.
Instead working around it might be worth spending the time fixing this
in JCL directly and make the whole world happy ;-)

cheers
--
Torsten

Mime
View raw message