cocoon-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Francesco Chicchiriccò <>
Subject Re: [C3] replacing the logging framework
Date Tue, 09 Aug 2011 14:04:57 GMT
On 20/07/2011 10:00, Francesco Chicchiriccò wrote:
> On 19/07/2011 13:46, Thorsten Scherler wrote:
>> On Wed, 2011-04-27 at 09:25 +0200, Simone Tripodi wrote:
>>> Hi all guys,
>>> thanks for your feedbacks, I didn't change any single line of code 
>>> indeed before hearing about possible side-effects.
>>> I agree with Jasha, let's release the alpha-3 first, then adding 
>>> improvements in future releases!
>> Should we pick that thread up again.
>> Do we have an issue open for this task?
> Now we do: COCOON3-69.

I've just committed all the modifications involved with this issue: now 
there should be no remaining trace of commons-logging or log4j 
throughout the source code, besides the necessary exclusions in some POM 

A couple of remarks:

1. I had to modify various source files: all the tests pass - well, at 
least on my Linux machine - but you never know about side effects, so 
please check if everything is still working after updating.

2. Among other things, I had to write a substitute for 
Log4JConfigurator, part of cocoon-spring-configurator; for the moment I 
put the new class (LogbackConfigurator) in cocoon-servlet, mainly 
because that module had all necessary dependencies and is included in 
cocoon-sample-webapp and cocoon-sample-wicket-webapp that are actually 
using cocoon-spring-configurator for configuring logging.
Of course, the right place is instead in cocoon-spring-configurator 
sources, so how could we handle this? Can I move that class to 
cocoon-spring-configurator's? In which SVN place? And how can we release 
a SNAPSHOT version of this subproject?


Francesco Chicchiriccò

Apache Cocoon Committer and PMC Member

View raw message