Mailing-List: contact ddlutils-dev-help@db.apache.org; run by ezmlm
Precedence: bulk
Reply-To: ddlutils-dev@db.apache.org
Message-ID: <28309312.1177302615611.JavaMail.jira@brutus>
Date: Sun, 22 Apr 2007 21:30:15 -0700 (PDT)
From: "Thomas Dudziak (JIRA)" <jira@apache.org>
To: ddlutils-dev@db.apache.org
Subject: [jira] Reopened: (DDLUTILS-168) DatabaseTaskBase should keep log4j
 configuration untouched
In-Reply-To: <20504439.1176133172431.JavaMail.jira@brutus>
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: quoted-printable


     [ https://issues.apache.org/jira/browse/DDLUTILS-168?page=3Dcom.atlass=
ian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Thomas Dudziak reopened DDLUTILS-168:
-------------------------------------


> 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=C2=B4s configuration=
 untouched. In current version, the implemented behaviour causes conflicts =
when running ant via its API from, say, a jmx inside JBoss.=20
> The symptom is the infamous log4j=C2=B4s  message "ERROR: invalid console=
 appender config detected, console stream is looping".
> In my private copy of ddlutils, I=C2=B4ve implemented a workaround by sur=
rounding most of  the code inside the function initLogging() with an "if ( =
 a sensible system property not found ) {  do log4j stuff }".
> Actually, I don=C2=B4t know why is this code there, anyway... The comment=
 in the code say that you=C2=B4re forcing console output, but makes no ment=
ion about the reasoning behind this decision.
> Should=C2=B4t log be simply delegated to commons-logging ?

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