http://bugzilla.slf4j.org/show_bug.cgi?id=196 --- Comment #2 from Richard Taylor <ryo.away@gmail.com> 2010-08-13 20:01:45 --- (In reply to comment #1)

If ReportNG has that strong a dependency on Log4J that it's trying to set the additivity of a category then I would say it's a hard dependency and not suitable for piping to SLF4J.

Think of it as a library in a webapp that casts HttpServletRequest to a Tomcat specific implementation. If your webapp depends on that library then you're stuck with Tomcat.

Log4j over slf4j is only meant to work with libraries that use the simplest methods on log4j - ie Logger.getLogger and then the trace/debug/info/warn/error methods. It isn't meant to support the whole log4j api.

I see your point. The purpose of this bug is to request expansion of the implementation. If that's not feasible or outside of the scope of the project, I'll resort to filing a bug with ReportNG to change their dependency. Let me know so I can proceed to the next action. -- Configure bugmail: http://bugzilla.slf4j.org/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are the assignee for the bug.

http://bugzilla.slf4j.org/show_bug.cgi?id=196 Richard Taylor <ryo.away@gmail.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEW |RESOLVED Resolution| |WONTFIX --- Comment #4 from Richard Taylor <ryo.away@gmail.com> 2010-08-13 21:08:20 --- (In reply to comment #3) I suppose you are right. Logback, the implementation we are using, could do something with additivity, but not via slf4j. We can't use slf4j-logj12 because we use log4j-over-slf4j for all other log4j dependencies in the application, since our design uses logback as the final logger. I will look into getting ReportNG to become compatible with slf4j, so I am dropping this bug. -- Configure bugmail: http://bugzilla.slf4j.org/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are the assignee for the bug.