ant-user mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Dominique Devienne <DDevie...@lgc.com>
Subject RE: Conditional if/unless echo
Date Thu, 10 Apr 2003 14:19:04 GMT
The level attribute is not that useful... Most of the time, we want to debug
or be more verbose about our own build logic, for the purpose of build users
to see, not build writer. Thus, getting all the Ant verbose or debug output
is not suitable, since drowns the important build-writer-specified
information. This is why <echo> should have an if/unless attribute (I'd even
add a ifTrue attribute, like I demonstrated with my <echopath> task).

This is so simple and useful, I just don't get why people pushed back on it
several time before... --DD

-----Original Message-----
From: Erik Hatcher [mailto:jakarta-ant@ehatchersolutions.com] 
Sent: Thursday, April 10, 2003 9:03 AM
To: Ant Users List
Subject: Re: Conditional if/unless echo

Gotcha.  You could still use an Ant property for the value of the 
'level' attribute, so essentially you could hide it by putting it at 
the debug level.  But your solution is grand also!

	Erik


> -----Original Message-----
> From: Erik Hatcher [mailto:jakarta-ant@ehatchersolutions.com]
> Sent: Thursday, April 10, 2003 9:37 AM
> To: Ant Users List
> Subject: Re: Conditional if/unless echo
>
>
> But <echo> supports the 'level' attribute, so you can control what gets
> echo'd by using -verbose, -debug, -quiet command-line switches.
>
> 	Erik

Mime
View raw message