You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@camel.apache.org by "Claus Ibsen (JIRA)" <ji...@apache.org> on 2009/12/18 07:21:52 UTC
[jira] Updated: (CAMEL-2229) switch to slf4j / logback by default
as we'll get accurate version information in stack traces, plus MDC support
(and neater ways to avoid the "if (LOG.isDebugEnabled())" stuff
[ https://issues.apache.org/activemq/browse/CAMEL-2229?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Claus Ibsen updated CAMEL-2229:
-------------------------------
Fix Version/s: (was: 2.2.0)
Future
> switch to slf4j / logback by default as we'll get accurate version information in stack traces, plus MDC support (and neater ways to avoid the "if (LOG.isDebugEnabled())" stuff
> --------------------------------------------------------------------------------------------------------------------------------------------------------------------------------
>
> Key: CAMEL-2229
> URL: https://issues.apache.org/activemq/browse/CAMEL-2229
> Project: Apache Camel
> Issue Type: Improvement
> Reporter: James Strachan
> Fix For: Future
>
>
> slf4j has an MDC API which would be very handy for selectively turning on tracing of certain kinds of routes
> in addition logback has support for the full jar version info in stack traces (which will help us support camel) so we should probably switch.
> its easy to mix and match slf4j with logback (there's a commons-logging API impl) - plus its easy to bridge both clogging & slf4j to logback (kinda like log4j), so we should probably just switch to slf4j.
> BTW there's a tool that auto-converts source code we should just use...
> http://slf4j.org/migrator.html
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.