Mailing-List: contact user-help@ant.apache.org; run by ezmlm
Precedence: bulk
Reply-To: "Ant Users List" <user@ant.apache.org>
Received-SPF: pass (herse.apache.org: local policy)
Content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: text/plain;
	charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
Subject: AW: How to silence errors in SQL task or log
Date: Wed, 21 Mar 2007 14:40:16 +0100
Message-ID: <EF39D77A486C234B9D9933091CE6D21E24F1EE@z011034.bk.fin.local>
Thread-Topic: How to silence errors in SQL task or log
Thread-Index: AcdrvcpkBaLD15veQwaFZXi2+nYCVgAAHytw
From: <Jan.Materne@rzf.fin-nrw.de>
To: <user@ant.apache.org>

Just some ideas ...

a) <record>
b) custom Logger
   - if a special output comes, it starts/ends logging
   - special output could be done with <echo level=3D"debug>


Jan=20

>-----Urspr=FCngliche Nachricht-----
>Von: Hans Schwaebli [mailto:hans_schwaebli@yahoo.com]=20
>Gesendet: Mittwoch, 21. M=E4rz 2007 14:35
>An: Ant Users List
>Betreff: Re: How to silence errors in SQL task or log
>
>Internal, external ... didn't matter for my question. There is=20
>a error stream which I would like to conveniently redirect.=20
>The easiest thing is in the Ant script itself. In one SQL call=20
>I want to redirect it, in another not. Setting SQL level=20
>globally to info would not fit. There are still ways to do it,=20
>but they add even more complexity with all its side effects.
>
>  If I decide to continue the SQL script in case of an error,=20
>it would be nice if Ant by default would not print the error=20
>stream then.
>  =20
>  Okay, another case where I didn't overlook anything and now=20
>know that it is digging in the dirt deeply because of "by=20
>design" stuff. Its not just Ant, but CruiseControl, CVS and=20
>other stuff with such things.
>  =20
> =20
>Steve Loughran <stevel@apache.org> wrote:
>  Hans Schwaebli wrote:
>> Can anybody tell my why cannot be used for the SQL task?
>
>because sql task is not executing an external program
>
>> I want to silence the errors if they occur when running the=20
>SQL task. But it didn't work. Any solution? Best would be to=20
>log all errors of a certain SQL task on info level. This=20
>flexibility I am missing.
>
>log through log4j and set your log4j properties file to log sql errors=20
>at info level?
>
>---------------------------------------------------------------------
>To unsubscribe, e-mail: user-unsubscribe@ant.apache.org
>For additional commands, e-mail: user-help@ant.apache.org
>
>
>
>=20
>---------------------------------
>Be a PS3 game guru.
>Get your game face on with the latest PS3 news and previews at=20
>Yahoo! Games.
>

---------------------------------------------------------------------
To unsubscribe, e-mail: user-unsubscribe@ant.apache.org
For additional commands, e-mail: user-help@ant.apache.org