Re: [eclipse.org-architecture-council] AC topic : How to configure slf4j

[John Arthorne <John_Arthorne@xxxxxxxxxx>]

This is a recurring topic... Here are some
pointers:

https://bugs.eclipse.org/bugs/show_bug.cgi?id=358968
http://wiki.eclipse.org/Architecture_Council/Meetings/June_14_2012

In absence of a more general solution
where bundles can contribute log configuration via an OSGi service, I think
platform could ship a logback configuration with reasonable defaults to
mitigate the problem a bit (eg, suppress anything below WARNING level and
write errors/warnings to console).

John




From:      
 "Oberhuber, Martin"
<Martin.Oberhuber@xxxxxxxxxxxxx>
To:      
 "eclipse.org-architecture-council@xxxxxxxxxxx"
<eclipse.org-architecture-council@xxxxxxxxxxx>, 
Date:      
 02/07/2013 06:30 PM
Subject:    
   [eclipse.org-architecture-council]
AC topic : How to configure        slf4j, log4j,
logback etc in a product
Sent by:    
   eclipse.org-architecture-council-bounces@xxxxxxxxxxx

---

Hi all,
 
Looking at 
 
    https://bugs.eclipse.org/bugs/show_bug.cgi?id=400027

 
I yesterday came across an issue that I
think has been discussed somewhere in the past:
With slf4j, log4j and logback installed
into Eclipse, and several bundles using those API’s
to perform logging, how can a product configure
the logging properly ?
 
The concrete problem was that one configuration
was logging too much into stdout,
and it’s unclear how to turn that off.
Coding some log configuration into a bundle
is also inappropriate since multiple bundles
would step on each other.
 
Seems like we need a policy / recommendation
for configuring logging.
 
Does anybody here on the list have experience
in that area, and/or can point us
to some previous discussions ? Any recommendation
for how to proceed ?
 
Thanks,
Martin
--
Martin Oberhuber, SMTS
/ Product Architect – Development Tools, Wind
River
direct +43.662.457915.85  fax
+43.662.457915.6
 _______________________________________________
eclipse.org-architecture-council mailing list
eclipse.org-architecture-council@xxxxxxxxxxx
https://dev.eclipse.org/mailman/listinfo/eclipse.org-architecture-council

IMPORTANT: Membership in this list is generated by processes internal to
the Eclipse Foundation.  To be permanently removed from this list,
you must contact emo@xxxxxxxxxxx to request removal.