On Mon, 05 May 2008 20:12:29 +0200, Ales Justin <ales.justin(a)gmail.com> wrote:
Weird that you have to modify some class, StaticLoggerBinder.
What you could do is just add a System property which would take a list
of possible new impls, and the check if they exist on the classpath via
reflection, taking the first one existing.
This is exactly why commons-logging was scrapped!
reflection is not usable across different deployment scenarios.
/max
> I'm more than willing to take a look at what it might take to
bridge
> slf4j and jboss-logging.
Reading that link looks like it shouldn't be hard.
And we can put this as new jboss-logging-slf4j module; making it both ways:
- slf4j --> slf4j-jboss-logging
- jboss-logging-spi --> jboss-logging-slf4j
_______________________________________________
jboss-development mailing list
jboss-development(a)lists.jboss.org
https://lists.jboss.org/mailman/listinfo/jboss-development