2011/8/3 Antonio Petrelli <antonio.petre...@gmail.com>

> However in my experience SLF4J has a big drawback: when used in a shared
> classloader (JBoss Portal anyone?) it is needed to have the same stinky old
> version of SLF4J in all applications during compile time, and the library
> should be excluded from the package.
>

Correcting myself, this is a flaw in JBoss Portal and/or the portlet
specification, because they need a shared classloader to work, the same
problem would happen using commons-logging.

Antonio

Reply via email to