db-ddlutils-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Philippe de M. Sevestre (JIRA)" <j...@apache.org>
Subject [jira] Created: (DDLUTILS-168) DatabaseTaskBase should keep log4j configuration untouched
Date Mon, 09 Apr 2007 15:39:32 GMT
DatabaseTaskBase should keep log4j configuration untouched

                 Key: DDLUTILS-168
                 URL: https://issues.apache.org/jira/browse/DDLUTILS-168
             Project: DdlUtils
          Issue Type: Improvement
          Components: Ant Tasks
         Environment: all
            Reporter: Philippe de M. Sevestre
         Assigned To: Thomas Dudziak
            Priority: Minor

DatabaseTaskBase should hava an option to keep log4j´s configuration untouched. In current
version, the implemented behaviour causes conflicts when running ant via its API from, say,
a jmx inside JBoss. 

The symptom is the infamous log4j´s  message "ERROR: invalid console appender config detected,
console stream is looping".

In my private copy of ddlutils, I´ve implemented a workaround by surrounding most of  the
code inside the function initLogging() with an "if (  a sensible system property not found
) {  do log4j stuff }".

Actually, I don´t know why is this code there, anyway... The comment in the code say that
you´re forcing console output, but makes no mention about the reasoning behind this decision.

Should´t log be simply delegated to commons-logging ?

This message is automatically generated by JIRA.
You can reply to this email to add a comment to the issue online.

View raw message