You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@jackrabbit.apache.org by "Tobias Bocanegra (JIRA)" <ji...@apache.org> on 2006/04/24 14:39:07 UTC

[jira] Created: (JCR-410) JCR-Server Code depends on Log4J directly

JCR-Server Code depends on Log4J directly
-----------------------------------------

         Key: JCR-410
         URL: http://issues.apache.org/jira/browse/JCR-410
     Project: Jackrabbit
        Type: Improvement

  Components: webdav  
    Versions: 0.9, 1.0    
    Reporter: Tobias Bocanegra
 Assigned to: Tobias Bocanegra 


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


[jira] Resolved: (JCR-410) JCR-Server Code depends on Log4J directly

Posted by "Tobias Bocanegra (JIRA)" <ji...@apache.org>.
     [ http://issues.apache.org/jira/browse/JCR-410?page=all ]
     
Tobias Bocanegra resolved JCR-410:
----------------------------------

    Fix Version: 1.1
     Resolution: Fixed

fixed.

Committed revision 396547.


> JCR-Server Code depends on Log4J directly
> -----------------------------------------
>
>          Key: JCR-410
>          URL: http://issues.apache.org/jira/browse/JCR-410
>      Project: Jackrabbit
>         Type: Improvement

>   Components: webdav
>     Versions: 1.0, 0.9
>     Reporter: Tobias Bocanegra
>     Assignee: Tobias Bocanegra
>      Fix For: 1.1

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


[jira] Updated: (JCR-410) JCR-Server Code depends on Log4J directly

Posted by "Tobias Bocanegra (JIRA)" <ji...@apache.org>.
     [ http://issues.apache.org/jira/browse/JCR-410?page=all ]

Tobias Bocanegra updated JCR-410:
---------------------------------

    Version: 0.9
             1.0
                 (was: 1.1)

> JCR-Server Code depends on Log4J directly
> -----------------------------------------
>
>          Key: JCR-410
>          URL: http://issues.apache.org/jira/browse/JCR-410
>      Project: Jackrabbit
>         Type: Improvement

>   Components: webdav
>     Versions: 0.9, 1.0
>     Reporter: Tobias Bocanegra
>     Assignee: Tobias Bocanegra

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


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

Posted by "Tobias Bocanegra (JIRA)" <ji...@apache.org>.
    [ http://issues.apache.org/jira/browse/JCR-410?page=comments#action_12376030 ] 

Tobias Bocanegra commented on JCR-410:
--------------------------------------

of course :-) i just copy-pasted the original text from issue JCR-215 without reading it :-|

> JCR-Server Code depends on Log4J directly
> -----------------------------------------
>
>          Key: JCR-410
>          URL: http://issues.apache.org/jira/browse/JCR-410
>      Project: Jackrabbit
>         Type: Improvement

>   Components: webdav
>     Versions: 1.0, 0.9
>     Reporter: Tobias Bocanegra
>     Assignee: Tobias Bocanegra

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


[jira] Kommentiert: (JCR-410) JCR-Server Code depends on Log4J directly

Posted by "Felix Meschberger (JIRA)" <ji...@apache.org>.
    [ http://issues.apache.org/jira/browse/JCR-410?page=comments#action_12376021 ] 

Felix Meschberger commented on JCR-410:
---------------------------------------

Shouldn't this actually be slf4j instead of commons-logging as the rest of JCR has gone that way ?

> JCR-Server Code depends on Log4J directly
> -----------------------------------------
>
>          Key: JCR-410
>          URL: http://issues.apache.org/jira/browse/JCR-410
>      Project: Jackrabbit
>         Type: Improvement

>   Components: webdav
>     Versions: 1.0, 0.9
>     Reporter: Tobias Bocanegra
>     Assignee: Tobias Bocanegra

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


[jira] Closed: (JCR-410) JCR-Server Code depends on Log4J directly

Posted by "Tobias Bocanegra (JIRA)" <ji...@apache.org>.
     [ http://issues.apache.org/jira/browse/JCR-410?page=all ]
     
Tobias Bocanegra closed JCR-410:
--------------------------------


> JCR-Server Code depends on Log4J directly
> -----------------------------------------
>
>          Key: JCR-410
>          URL: http://issues.apache.org/jira/browse/JCR-410
>      Project: Jackrabbit
>         Type: Improvement

>   Components: webdav
>     Versions: 1.0, 0.9
>     Reporter: Tobias Bocanegra
>     Assignee: Tobias Bocanegra
>      Fix For: 1.1

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