Hello, I do like the concept of SLF4J very much - it is interface based and very easy to use: simply change one jar.
There were some discussions on the JCL mailing list to stop any further development and with an approach to use JUL as default for any (new) commons libraries. I have created a JCL version (called 2.0.0) in the style of SLF4J. I hope this is seen as "learning by example of a good design" and not as stealing an idea by most SLF4J developers. Regards Boris Mail on commons-dev > Hello, > > I have seen the recent discussions on JCL 2.0.0 and a version without > autodiscovery. > Someone stated to stop any further development (with good reasons > behind) but I am > thinking different. > > Please have a look at the (working) code: > https://issues.apache.org/jira/browse/LOGGING-112 > > It has a static binding, some improvements in the logfactories > (recognizes native implementations). > API and implementations are cleanly separated, the 1.1.x diagnostic > function is still used. > > What are your thoughts? > Is this a possible direction? > > Is it worth to put more time and energy into this? > > Regards > Boris > _______________________________________________ dev mailing list [email protected] http://www.slf4j.org/mailman/listinfo/dev
