[ http://issues.apache.org/jira/browse/JCR-215?page=comments#action_12329339 ]
Jukka Zitting commented on JCR-215: ----------------------------------- There was a discussion [1] on the mailing list about this early this year. The conclusion [2] was to wait for the toolkit-independent UGLI layer to mature. Since then the UGLI project [3] has been renamed and moved to the Simple Logging Facade for Java (SLF4J) project [4] that is currently at beta 7 of version 1.0. The SLF4J beta jars are already available at the Ibiblio Maven repository. I believe now would be a good time to migrate from log4j to slf4j. Any objections? [1] http://thread.gmane.org/gmane.comp.apache.jackrabbit.devel/740 [2] http://article.gmane.org/gmane.comp.apache.jackrabbit.devel/898 [3] http://logging.apache.org/log4j/docs/ugli.html [4] http://www.slf4j.org/ > Code is depends on Log4J directly instead of commons-logging > ------------------------------------------------------------ > > Key: JCR-215 > URL: http://issues.apache.org/jira/browse/JCR-215 > Project: Jackrabbit > Type: Bug > Versions: 1.0 > Reporter: Ragy Eleish > Priority: Critical > > The code is written against the Log4J APIs, which forces all users of > Jackarabbit to pick up log4J dependency and to juggle with JDK logging and > Log4J configuration if other components of the project uses JDK 1.4 logging. > If the code is move to depend on Apache commons-logging this issue will be > resolved. Also this should be a minor fix. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://issues.apache.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
