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

Posted to notifications@asterixdb.apache.org by "Till (JIRA)" <ji...@apache.org> on 2016/11/29 00:25:58 UTC

[jira] [Updated] (ASTERIXDB-1564) Consistently use log4j

     [ https://issues.apache.org/jira/browse/ASTERIXDB-1564?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Till updated ASTERIXDB-1564:
----------------------------
    Description: Right now we use a mix of log4j and java.util.logging. We should consistently use log4j. Among other things to be able to use the same formatter for all logging.  (was: Right now we use a mix of log4j and java.util.logging. We should consistently use java.util.logging. Among other things to be able to use the same formatter for all logging.)
        Summary: Consistently use log4j  (was: Consistently use java.util.logging)

Some discussion a few weeks ago convinced me, that log4j is the better choice.

> Consistently use log4j
> ----------------------
>
>                 Key: ASTERIXDB-1564
>                 URL: https://issues.apache.org/jira/browse/ASTERIXDB-1564
>             Project: Apache AsterixDB
>          Issue Type: Bug
>          Components: AsterixDB, Monitoring/Admin
>            Reporter: Till
>            Assignee: Till
>            Priority: Critical
>
> Right now we use a mix of log4j and java.util.logging. We should consistently use log4j. Among other things to be able to use the same formatter for all logging.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)