Thread: [Rails-devel] Update of the logging framework

Status: Beta

Brought to you by: neutronc, wakko666

rails-devel

[Rails-devel] Update of the logging framework

From: Stefan F. <ste...@we...> - 2012-06-01 15:36:31

Erik & Brett:
taking the opportunity of a major update to Rails 2.0 I suggest to 
replace the log4j logging by the combination of sl4j and logback.

See http://slf4j.org/ and http://logback.qos.ch/index.html for details.

Any objections?

Stefan

Re: [Rails-devel] Update of the logging framework

From: brett l. <bre...@gm...> - 2012-06-01 15:41:06

Stefan -

I don't object to it outright, but I would like to see more info on
why such a change is being made before it's implemented.

What limitations of log4j would we be overcoming?
What essential features does sl4j and logback have that log4j doesn't?
Would updating log4j change the comparison any?

I'm not really tied to one solution over another, but I'd like to
understand what we're gaining or losing by switching.

---Brett.

On Fri, Jun 1, 2012 at 11:36 AM, Stefan Frey <ste...@we...> wrote:
> Erik & Brett:
> taking the opportunity of a major update to Rails 2.0 I suggest to
> replace the log4j logging by the combination of sl4j and logback.
>
> See http://slf4j.org/ and http://logback.qos.ch/index.html for details.
>
> Any objections?
>
> Stefan
>
> ------------------------------------------------------------------------------
> Live Security Virtual Conference
> Exclusive live event will cover all the ways today's security and
> threat landscape has changed and how IT managers can respond. Discussions
> will include endpoint security, mobile security and the latest in malware
> threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/
> _______________________________________________
> Rails-devel mailing list
> Rai...@li...
> https://lists.sourceforge.net/lists/listinfo/rails-devel

Re: [Rails-devel] Update of the logging framework

From: Stefan F. <ste...@we...> - 2012-06-01 15:56:44

Brett:
Main limitation is the much better documentation. And there is not much 
documentation on log4j except the api and few introductory documents. 
Compare this to one below.

The reason I had to look for documentation was mainly how to 
include/enable/disable the log4j logging during unit testing.

And from the developers involved logback is log4j version 2 anyway.

Stefan

On 06/01/2012 05:40 PM, brett lentz wrote:
> Stefan -
>
> I don't object to it outright, but I would like to see more info on
> why such a change is being made before it's implemented.
>
> What limitations of log4j would we be overcoming?
> What essential features does sl4j and logback have that log4j doesn't?
> Would updating log4j change the comparison any?
>
> I'm not really tied to one solution over another, but I'd like to
> understand what we're gaining or losing by switching.
>
> ---Brett.
>
>
> On Fri, Jun 1, 2012 at 11:36 AM, Stefan Frey<ste...@we...>  wrote:
>> Erik&  Brett:
>> taking the opportunity of a major update to Rails 2.0 I suggest to
>> replace the log4j logging by the combination of sl4j and logback.
>>
>> See http://slf4j.org/ and http://logback.qos.ch/index.html for details.
>>
>> Any objections?
>>
>> Stefan
>>
>> ------------------------------------------------------------------------------
>> Live Security Virtual Conference
>> Exclusive live event will cover all the ways today's security and
>> threat landscape has changed and how IT managers can respond. Discussions
>> will include endpoint security, mobile security and the latest in malware
>> threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/
>> _______________________________________________
>> Rails-devel mailing list
>> Rai...@li...
>> https://lists.sourceforge.net/lists/listinfo/rails-devel
>
> ------------------------------------------------------------------------------
> Live Security Virtual Conference
> Exclusive live event will cover all the ways today's security and
> threat landscape has changed and how IT managers can respond. Discussions
> will include endpoint security, mobile security and the latest in malware
> threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/
> _______________________________________________
> Rails-devel mailing list
> Rai...@li...
> https://lists.sourceforge.net/lists/listinfo/rails-devel

Re: [Rails-devel] Update of the logging framework

From: brett l. <bre...@gm...> - 2012-06-01 16:06:22

Stefan -

That's good enough for me. Using better-supported, better-documented
tools is a win. :-)

---Brett.


On Fri, Jun 1, 2012 at 11:56 AM, Stefan Frey <ste...@we...> wrote:
> Brett:
> Main limitation is the much better documentation. And there is not much
> documentation on log4j except the api and few introductory documents.
> Compare this to one below.
>
> The reason I had to look for documentation was mainly how to
> include/enable/disable the log4j logging during unit testing.
>
> And from the developers involved logback is log4j version 2 anyway.
>
> Stefan
>
> On 06/01/2012 05:40 PM, brett lentz wrote:
>> Stefan -
>>
>> I don't object to it outright, but I would like to see more info on
>> why such a change is being made before it's implemented.
>>
>> What limitations of log4j would we be overcoming?
>> What essential features does sl4j and logback have that log4j doesn't?
>> Would updating log4j change the comparison any?
>>
>> I'm not really tied to one solution over another, but I'd like to
>> understand what we're gaining or losing by switching.
>>
>> ---Brett.
>>
>>
>> On Fri, Jun 1, 2012 at 11:36 AM, Stefan Frey<ste...@we...>  wrote:
>>> Erik&  Brett:
>>> taking the opportunity of a major update to Rails 2.0 I suggest to
>>> replace the log4j logging by the combination of sl4j and logback.
>>>
>>> See http://slf4j.org/ and http://logback.qos.ch/index.html for details.
>>>
>>> Any objections?
>>>
>>> Stefan
>>>
>>> ------------------------------------------------------------------------------
>>> Live Security Virtual Conference
>>> Exclusive live event will cover all the ways today's security and
>>> threat landscape has changed and how IT managers can respond. Discussions
>>> will include endpoint security, mobile security and the latest in malware
>>> threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/
>>> _______________________________________________
>>> Rails-devel mailing list
>>> Rai...@li...
>>> https://lists.sourceforge.net/lists/listinfo/rails-devel
>>
>> ------------------------------------------------------------------------------
>> Live Security Virtual Conference
>> Exclusive live event will cover all the ways today's security and
>> threat landscape has changed and how IT managers can respond. Discussions
>> will include endpoint security, mobile security and the latest in malware
>> threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/
>> _______________________________________________
>> Rails-devel mailing list
>> Rai...@li...
>> https://lists.sourceforge.net/lists/listinfo/rails-devel
>
>
> ------------------------------------------------------------------------------
> Live Security Virtual Conference
> Exclusive live event will cover all the ways today's security and
> threat landscape has changed and how IT managers can respond. Discussions
> will include endpoint security, mobile security and the latest in malware
> threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/
> _______________________________________________
> Rails-devel mailing list
> Rai...@li...
> https://lists.sourceforge.net/lists/listinfo/rails-devel

Re: [Rails-devel] Update of the logging framework

From: Erik V. <eri...@xs...> - 2012-06-01 19:30:34

I consider log4j good enough, but I have no real objections.  

In an slf4j example I noticed the use of {} placeholders in the logged text, with arguments, and I like that. 
On first sight, logback looks slightly better than log4j.  Not sure if the documentation is that much better, though: I had to click around for a while before I found a few more than trivial code examples. But I guess that's just me.

Go ahead if you prefer it.

Erik.

> -----Original Message-----
> From: brett lentz [mailto:bre...@gm...]
> Sent: Friday, June 01, 2012 6:06 PM
> To: Development list for Rails: an 18xx game
> Subject: Re: [Rails-devel] Update of the logging framework
> 
> Stefan -
> 
> That's good enough for me. Using better-supported, better-documented
> tools is a win. :-)
> 
> ---Brett.
> 
> 
> On Fri, Jun 1, 2012 at 11:56 AM, Stefan Frey <ste...@we...> wrote:
> > Brett:
> > Main limitation is the much better documentation. And there is not
> > much documentation on log4j except the api and few introductory
> documents.
> > Compare this to one below.
> >
> > The reason I had to look for documentation was mainly how to
> > include/enable/disable the log4j logging during unit testing.
> >
> > And from the developers involved logback is log4j version 2 anyway.
> >
> > Stefan
> >
> > On 06/01/2012 05:40 PM, brett lentz wrote:
> >> Stefan -
> >>
> >> I don't object to it outright, but I would like to see more info on
> >> why such a change is being made before it's implemented.
> >>
> >> What limitations of log4j would we be overcoming?
> >> What essential features does sl4j and logback have that log4j doesn't?
> >> Would updating log4j change the comparison any?
> >>
> >> I'm not really tied to one solution over another, but I'd like to
> >> understand what we're gaining or losing by switching.
> >>
> >> ---Brett.
> >>
> >>
> >> On Fri, Jun 1, 2012 at 11:36 AM, Stefan
> Frey<ste...@we...>  wrote:
> >>> Erik&  Brett:
> >>> taking the opportunity of a major update to Rails 2.0 I suggest to
> >>> replace the log4j logging by the combination of sl4j and logback.
> >>>
> >>> See http://slf4j.org/ and http://logback.qos.ch/index.html for details.
> >>>
> >>> Any objections?
> >>>
> >>> Stefan
> >>>
> >>> --------------------------------------------------------------------
> >>> ----------
> >>> Live Security Virtual Conference
> >>> Exclusive live event will cover all the ways today's security and
> >>> threat landscape has changed and how IT managers can respond.
> >>> Discussions will include endpoint security, mobile security and the
> >>> latest in malware threats.
> >>> http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/
> >>> _______________________________________________
> >>> Rails-devel mailing list
> >>> Rai...@li...
> >>> https://lists.sourceforge.net/lists/listinfo/rails-devel
> >>
> >> ---------------------------------------------------------------------
> >> ---------
> >> Live Security Virtual Conference
> >> Exclusive live event will cover all the ways today's security and
> >> threat landscape has changed and how IT managers can respond.
> >> Discussions will include endpoint security, mobile security and the
> >> latest in malware threats.
> >> http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/
> >> _______________________________________________
> >> Rails-devel mailing list
> >> Rai...@li...
> >> https://lists.sourceforge.net/lists/listinfo/rails-devel
> >
> >
> > ----------------------------------------------------------------------
> > --------
> > Live Security Virtual Conference
> > Exclusive live event will cover all the ways today's security and
> > threat landscape has changed and how IT managers can respond.
> > Discussions will include endpoint security, mobile security and the
> > latest in malware threats.
> > http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/
> > _______________________________________________
> > Rails-devel mailing list
> > Rai...@li...
> > https://lists.sourceforge.net/lists/listinfo/rails-devel
> 
> ------------------------------------------------------------------------------
> Live Security Virtual Conference
> Exclusive live event will cover all the ways today's security and threat
> landscape has changed and how IT managers can respond. Discussions will
> include endpoint security, mobile security and the latest in malware threats.
> http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/
> _______________________________________________
> Rails-devel mailing list
> Rai...@li...
> https://lists.sourceforge.net/lists/listinfo/rails-devel