Skip to main content


Eclipse Community Forums
Forum Search:

Search      Help    Register    Login    Home
Home » Eclipse Projects » Orbit » Bug 313502 fixed: how to configure the logging (SLF4J/Logback/log4j)
Bug 313502 fixed: how to configure the logging (SLF4J/Logback/log4j) [message #541335] Sun, 20 June 2010 08:17 Go to next message
Michael Pellaton is currently offline Michael PellatonFriend
Messages: 289
Registered: July 2009
Senior Member
Hi

I am glad, Bug 313502 got fixed quickly, but now I have another
question:

When I install Mylyn + XText everthing works finde and I get the
following bundles installed:
- ch.qos.logback.slf4j_0.9.19.v20100519-1910.jar
- org.slf4j.api_1.5.11.v20100519-1910.jar
- org.slf4j.jcl_1.5.11.v20100419-1106.jar

I start Eclipse from the console and as there is no log configuration,
the console is 'spammed' with debug messages. As I understand the issue,
this is because there is no logging configuration.

Where and how can I add a logback configuration? In a plugin? In a
fragment to which host bundle? ...

Any hints welcome!

Michael
PS: the same question arises with log4j...

Report message to a moderator

Re: Bug 313502 fixed: how to configure the logging (SLF4J/Logback/log4j) [message #542135 is a reply to message #541335] Thu, 24 June 2010 02:04 Go to previous messageGo to next message
David Williams is currently offline David WilliamsFriend
Messages: 176
Registered: July 2009
Senior Member
>
> I am glad, Bug 313502 got fixed quickly, but now I have another
> question:
>
> When I install Mylyn + XText everthing works finde and I get the
> following bundles installed:
> - ch.qos.logback.slf4j_0.9.19.v20100519-1910.jar
> - org.slf4j.api_1.5.11.v20100519-1910.jar
> - org.slf4j.jcl_1.5.11.v20100419-1106.jar
>
> I start Eclipse from the console and as there is no log configuration,
> the console is 'spammed' with debug messages. As I understand the issue,
> this is because there is no logging configuration.
>
> Where and how can I add a logback configuration? In a plugin? In a
> fragment to which host bundle? ...
>

I'd guess a fragment, but don't know to which host bundle. You might ask
as a comment/question in that bug .. as the experts would be more likely
to see that, than this newsgroup.

Earlier in that bug, is does say "intervention is required" and gives a
reference to
http://www.slf4j.org/codes.html#StaticLoggerBinder
where its is explained in the next release (1.6) that a "no op" logger
will be built in as the default. Until then ... I think you do need to
provide one in a fragment? (but, I'm no expert).

Let us know what you learn if/when you solve the problem. I have a
feeling it will come up again.

Report message to a moderator

Re: Bug 313502 fixed: how to configure the logging (SLF4J/Logback/log4j) [message #542419 is a reply to message #542135] Thu, 24 June 2010 18:26 Go to previous messageGo to next message
Michael Pellaton is currently offline Michael PellatonFriend
Messages: 289
Registered: July 2009
Senior Member
Hi

In the meantime, I found out by trial and error how it works: One needs
to provide a logback.xml configuration file in a fragment with host
bundle ch.qos.logback.core.

Take care,
Michael

Report message to a moderator

Re: Bug 313502 fixed: how to configure the logging (SLF4J/Logback/log4j) [message #565762 is a reply to message #541335] Thu, 24 June 2010 02:04 Go to previous messageGo to next message
David Williams is currently offline David WilliamsFriend
Messages: 176
Registered: July 2009
Senior Member
>
> I am glad, Bug 313502 got fixed quickly, but now I have another
> question:
>
> When I install Mylyn + XText everthing works finde and I get the
> following bundles installed:
> - ch.qos.logback.slf4j_0.9.19.v20100519-1910.jar
> - org.slf4j.api_1.5.11.v20100519-1910.jar
> - org.slf4j.jcl_1.5.11.v20100419-1106.jar
>
> I start Eclipse from the console and as there is no log configuration,
> the console is 'spammed' with debug messages. As I understand the issue,
> this is because there is no logging configuration.
>
> Where and how can I add a logback configuration? In a plugin? In a
> fragment to which host bundle? ...
>

I'd guess a fragment, but don't know to which host bundle. You might ask
as a comment/question in that bug .. as the experts would be more likely
to see that, than this newsgroup.

Earlier in that bug, is does say "intervention is required" and gives a
reference to
http://www.slf4j.org/codes.html#StaticLoggerBinder
where its is explained in the next release (1.6) that a "no op" logger
will be built in as the default. Until then ... I think you do need to
provide one in a fragment? (but, I'm no expert).

Let us know what you learn if/when you solve the problem. I have a
feeling it will come up again.

Report message to a moderator

Re: Bug 313502 fixed: how to configure the logging (SLF4J/Logback/log4j) [message #565817 is a reply to message #542135] Thu, 24 June 2010 18:26 Go to previous messageGo to next message
Michael Pellaton is currently offline Michael PellatonFriend
Messages: 289
Registered: July 2009
Senior Member
Hi

In the meantime, I found out by trial and error how it works: One needs
to provide a logback.xml configuration file in a fragment with host
bundle ch.qos.logback.core.

Take care,
Michael

Report message to a moderator

Re: Bug 313502 fixed: how to configure the logging (SLF4J/Logback/log4j) [message #648281 is a reply to message #541335] Wed, 12 January 2011 09:22 Go to previous message
Daniel FEDE is currently offline Daniel FEDEFriend
Messages: 1
Registered: January 2011
Junior Member
hi,

in the new version of logback (0.9.27) the fragment config only works with ch.qos.logback.classic as host plugin.

t c
daniel

Report message to a moderator

Previous Topic:SLF4j Version 1.6.0
Next Topic:[solr] cannot use CommonsHttpSolrServer 'coz impl package is not exported
Goto Forum:
  

[ Syndicate this forum (XML) ] [ RSS ]

Current Time: Tue Apr 23 13:40:08 GMT 2024

Powered by FUDForum. Page generated in 0.03631 seconds
.:: Contact :: Home ::.

Powered by: FUDforum 3.0.2.
Copyright ©2001-2010 FUDforum Bulletin Board Software

Back to the top

Sign up to our Newsletter

A fresh new issue delivered monthly