gora-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Enis Soztutar (Commented) (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (GORA-77) Replace commons logging with Log4j
Date Mon, 16 Jan 2012 18:01:41 GMT

    [ https://issues.apache.org/jira/browse/GORA-77?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13187048#comment-13187048

Enis Soztutar commented on GORA-77:

Lewis, can you elaborate on the advantages of using directly log4j APIs instead of commons
logging. Most of the projects I have dealt with either uses commons or slf4j, honestly, I
have never used the log4j api directly. 
> Replace commons logging with Log4j
> ----------------------------------
>                 Key: GORA-77
>                 URL: https://issues.apache.org/jira/browse/GORA-77
>             Project: Gora
>          Issue Type: Improvement
>          Components: documentation
>    Affects Versions: 0.1.1-incubating
>            Reporter: Lewis John McGibbney
>            Priority: Minor
>             Fix For: 0.2-incubating
> Log4j provides a richer logging resource, Gora would benefit accordingly. I propose to
implement Log4j 1.2.16 to replace all commons logging imports and code. 

This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira


View raw message