ant-user mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Echlin, Robert" <>
Subject RE: ant exec task message priority
Date Thu, 14 Jul 2011 13:45:23 GMT
Hudson must be matching some specific string to identify ERROR, INFO, etc.
Any change to that string would cause Hudson's match to fail.

Any chance there is a change in C compiler co-incidentally here?
Maybe some whitespace is being compressed as it passes through Ant?
I would pipe the output of Ant directly to a file, for each of the two versions, 
and a single version of compiler/make.
Then compare the two files. They might not be identical.

I haven't configured Hudson, so I can't tell you how to edit its string matching for your
C compiler.


> -----Original Message-----
> From: Stefan Bodewig []
> Sent: Thursday, July 14, 2011 7:33 AM
> To:
> Subject: Re: ant exec task message priority
> On 2011-07-12, Adam Bruss wrote:
> > ant 1.7.0 would naturally classify messages from make with priorities of
> info, warning or error.
> > ant 1.8.2 classifies all messages from make as priority info!
> Ant really only reads stderr and stdout from make. For everything that goes
> to stderr it will use ERROR and for everything that goes to stdout it will use
> INFO - and I don't recall any changes here.  At least this is the default
> behaviour unless you configure <exec> via its output related attributes or a
> nested redirector.
> Stefan
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: For additional
> commands, e-mail:

To unsubscribe, e-mail:
For additional commands, e-mail:

View raw message