You are viewing a plain text version of this content. The canonical link for it is here.

Posted to dev@jackrabbit.apache.org by "Jukka Zitting (JIRA)" <ji...@apache.org> on 2006/03/12 15:56:46 UTC

[jira] Commented: (JCR-215) Code depends on Log4J directly

    [ http://issues.apache.org/jira/browse/JCR-215?page=comments#action_12370070 ] 

Jukka Zitting commented on JCR-215:
-----------------------------------

Switched to SLF4J 1.0 logging in revision 385280. Targetting for inclusion in 1.0 unless anyone runs into trouble with SLF4J.

> Code depends on Log4J directly
> ------------------------------
>
>          Key: JCR-215
>          URL: http://issues.apache.org/jira/browse/JCR-215
>      Project: Jackrabbit
>         Type: Improvement
>     Reporter: Ragy Eleish
>     Assignee: Jukka Zitting
>     Priority: Minor
>      Fix For: 1.1
>  Attachments: jackrabbit.slf4j.patch, jackrabbit.slf4j.r293110.patch
>
> 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