commons-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Antonio Petrelli <>
Subject Re: [logging] logging vs slf4j
Date Wed, 03 Aug 2011 18:18:34 GMT
2011/8/3 Antonio Petrelli <>

> 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.


  • Unnamed multipart/alternative (inline, None, 0 bytes)
View raw message