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

Posted to issues@commons.apache.org by "Sebb (JIRA)" <ji...@apache.org> on 2012/07/18 18:15:34 UTC

[jira] [Commented] (LOGGING-142) Log4JLogger uses deprecated static members of Priority such as INFO

    [ https://issues.apache.org/jira/browse/LOGGING-142?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13417205#comment-13417205 ] 

Sebb commented on LOGGING-142:
------------------------------

In 1.0.4, the code used both Level and Priority.

The reason for this was that it was thought that log4j 1.3 was likely to change Level so it no longer extended Priority.
However, 1.3 never really happened; 1.3 was only released as alpha code.
                
> Log4JLogger uses deprecated static members of Priority such as INFO
> -------------------------------------------------------------------
>
>                 Key: LOGGING-142
>                 URL: https://issues.apache.org/jira/browse/LOGGING-142
>             Project: Commons Logging
>          Issue Type: Bug
>    Affects Versions: 1.1.1
>            Reporter: Jingguo Yao
>         Attachments: LOGGING-142.patch
>
>   Original Estimate: 2h
>  Remaining Estimate: 2h
>
> In version 1.1.1, Log4JLogger uses deprecated static members of Priority such as INFO to construct LoggingEvent. In version 1.0.4, static members from Level are used rather than from Priority. I think that this is a regression.

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