[
https://issues.apache.org/jira/browse/DDLUTILS-168?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Thomas Dudziak resolved DDLUTILS-168.
-------------------------------------
Resolution: Fixed
Fix Version/s: 1.0
I've added a simpleLogging parameter to the tasks which controls whether the
tasks configure logging themselves or not.
> 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
> Fix For: 1.0
>
>
> 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.
