jackrabbit-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Jukka Zitting (JIRA)" <j...@apache.org>
Subject [jira] Updated: (JCR-215) Code is depends on Log4J directly instead of commons-logging
Date Sun, 02 Oct 2005 13:43:49 GMT
     [ http://issues.apache.org/jira/browse/JCR-215?page=all ]

Jukka Zitting updated JCR-215:
------------------------------

    Attachment: jackrabbit.slf4j.r293110.patch

Updated the patch to apply cleanly to the latest sources (revision 293110). I'm having second
thoughts about applying the patch just yet, as the slf4j 1.0 beta releases seem to have had
some minor API changes along the way. It's probably better to wait for the official 1.0 release.

> 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: Improvement
>     Reporter: Ragy Eleish
>     Assignee: Jukka Zitting
>     Priority: Minor
>      Fix For: 1.0
>  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


Mime
View raw message