You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@cocoon.apache.org by Simone Tripodi <si...@apache.org> on 2011/04/23 16:56:03 UTC
[C3] replacing the logging framework
Hi all guys,
Reinhard, Francesco and I had a quick chat on tweeter about replacing
the logging framework in C3 and we all agreed on migrating to SLF4J +
Logback.
IMHO it is an operation simple enough that can be completed before
proceeding to next release, what does someone else think about it?
If there isn't any objection, I can take easily take care of it, just
let me know!
Have a nice day, all the best,
Simo
http://people.apache.org/~simonetripodi/
http://www.99soft.org/
Re: [C3] replacing the logging framework
Posted by Francesco Chicchiriccò <ch...@gmail.com>.
Simone Tripodi <si...@apache.org> wrote:
>Hi all guys,
>Reinhard, Francesco and I had a quick chat on tweeter about replacing
>the logging framework in C3 and we all agreed on migrating to SLF4J +
>Logback.
>IMHO it is an operation simple enough that can be completed before
>proceeding to next release, what does someone else think about it?
>If there isn't any objection, I can take easily take care of it, just
>let me know!
Go Simone, go!!! :-)
--
Apache Cocoon Committer and PMC Member
http://people.apache.org/~ilgrosso/
Re: [C3] replacing the logging framework
Posted by Francesco Chicchiriccò <il...@apache.org>.
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.
Gents,
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
files.
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?
TIA.
Regards.
--
Francesco Chicchiriccò
Apache Cocoon Committer and PMC Member
http://people.apache.org/~ilgrosso/
Re: [C3] replacing the logging framework
Posted by Francesco Chicchiriccò <il...@apache.org>.
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.
Thanks!
--
Francesco Chicchiriccò
Apache Cocoon Committer and PMC Member
http://people.apache.org/~ilgrosso/
Re: [C3] replacing the logging framework
Posted by Thorsten Scherler <sc...@gmail.com>.
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?
salu2
--
Thorsten Scherler <thorsten.at.apache.org>
codeBusters S.L. - web based systems
<consulting, training and solutions>
http://www.codebusters.es/
Re: [C3] replacing the logging framework
Posted by Reinhard Pötz <re...@apache.org>.
On 04/27/2011 09:25 AM, Simone Tripodi wrote:
> I can take care of making the release - any advice before I start? :)
see https://svn.apache.org/repos/asf/cocoon/cocoon3/trunk/RELEASE_HOWTO.txt
you can also contact me via Skype if you have any questions. Good luck ;-)
--
Reinhard Pötz Founder & Managing Director, Indoqa and Deepsearch
http://www.indoqa.com/people/reinhard-poetz.html
Member of the Apache Software Foundation
Apache Cocoon Committer, PMC member reinhard@apache.org
________________________________________________________________________
Furthermore, I think Oracle has to honor the JSPA agreement.
http://s.apache.org/JCPIsDead http://s.apache.org/tck-trap
Re: [C3] replacing the logging framework
Posted by Simone Tripodi <si...@apache.org>.
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!
I can take care of making the release - any advice before I start? :)
Thanks in advance, have a nice day!!!
Simo
http://people.apache.org/~simonetripodi/
http://www.99soft.org/
On Tue, Apr 26, 2011 at 1:26 PM, Jasha Joachimsthal
<j....@onehippo.com> wrote:
>
> On 26 April 2011 13:24, Reinhard Pötz <re...@apache.org> wrote:
>>
>> On 04/23/2011 04:56 PM, Simone Tripodi wrote:
>>>
>>> Hi all guys,
>>> Reinhard, Francesco and I had a quick chat on tweeter about replacing
>>> the logging framework in C3 and we all agreed on migrating to SLF4J +
>>> Logback.
>>> IMHO it is an operation simple enough that can be completed before
>>> proceeding to next release, what does someone else think about it?
>>> If there isn't any objection, I can take easily take care of it, just
>>> let me know!
>>
>> I guess you're right with the pipeline and sitemap modules, but I expect
>> it to be more difficult for the servlet module.
>>
>> The question _for now_ is whether we have to replace the logging framework
>> there at all and keep the Spring configurator's log4j integration instead.
>> Changing the servlet module to use the slf4j/log4j binding could be done
>> later.
>>
>> But I'm not sure if this plan works as expected ...
>
> I think we've been waiting for the alpha-3 release long enough. Why not ship
> it as is and then do the logging framework changes in an alpha-4 release?
> Jasha Joachimsthal
>
> j.joachimsthal@onehippo.com - jasha@apache.org
>
> Hippo
> Europe • Amsterdam • Oosteinde 11 • 1017 WT Amsterdam • +31 (0)20
> 522 4466
> USA • Boston • 1 Broadway • Cambridge, MA 02142 • +1 877 414 4776
> (toll free)
> www.onehippo.com • www.onehippo.org • info@onehippo.com
>
Re: [C3] replacing the logging framework
Posted by Jasha Joachimsthal <j....@onehippo.com>.
On 26 April 2011 13:24, Reinhard Pötz <re...@apache.org> wrote:
> On 04/23/2011 04:56 PM, Simone Tripodi wrote:
>
>> Hi all guys,
>> Reinhard, Francesco and I had a quick chat on tweeter about replacing
>> the logging framework in C3 and we all agreed on migrating to SLF4J +
>> Logback.
>> IMHO it is an operation simple enough that can be completed before
>> proceeding to next release, what does someone else think about it?
>> If there isn't any objection, I can take easily take care of it, just
>> let me know!
>>
>
> I guess you're right with the pipeline and sitemap modules, but I expect it
> to be more difficult for the servlet module.
>
> The question _for now_ is whether we have to replace the logging framework
> there at all and keep the Spring configurator's log4j integration instead.
> Changing the servlet module to use the slf4j/log4j binding could be done
> later.
>
> But I'm not sure if this plan works as expected ...
>
I think we've been waiting for the alpha-3 release long enough. Why not ship
it as is and then do the logging framework changes in an alpha-4 release?
Jasha Joachimsthal
j.joachimsthal@onehippo.com - jasha@apache.org
Hippo
Europe • Amsterdam • Oosteinde 11 • 1017 WT Amsterdam • +31 (0)20
522 4466
USA • Boston • 1 Broadway • Cambridge, MA 02142 • +1 877 414 4776
(toll free)
www.onehippo.com • www.onehippo.org • info@onehippo.com
Re: [C3] replacing the logging framework
Posted by Reinhard Pötz <re...@apache.org>.
On 04/23/2011 04:56 PM, Simone Tripodi wrote:
> Hi all guys,
> Reinhard, Francesco and I had a quick chat on tweeter about replacing
> the logging framework in C3 and we all agreed on migrating to SLF4J +
> Logback.
> IMHO it is an operation simple enough that can be completed before
> proceeding to next release, what does someone else think about it?
> If there isn't any objection, I can take easily take care of it, just
> let me know!
I guess you're right with the pipeline and sitemap modules, but I expect
it to be more difficult for the servlet module.
The question _for now_ is whether we have to replace the logging
framework there at all and keep the Spring configurator's log4j
integration instead. Changing the servlet module to use the slf4j/log4j
binding could be done later.
But I'm not sure if this plan works as expected ...
--
Reinhard Pötz Founder & Managing Director, Indoqa and Deepsearch
http://www.indoqa.com/people/reinhard-poetz.html
Member of the Apache Software Foundation
Apache Cocoon Committer, PMC member reinhard@apache.org
________________________________________________________________________
Furthermore, I think Oracle has to honor the JSPA agreement.
http://s.apache.org/JCPIsDead http://s.apache.org/tck-trap