. Januar 2010 08:25
To: Ant Users List
Subject: AW: ant log/output vs. unless/if on a target
Hello,
Write your own logger, that runs internally with verbose, but filters out what
you want.
Greetings Juergen
--
Jürgen Knuplesch
-Ursprüngliche Nachricht-
Von: Thomas Menzel [mailto:tmen
log/output vs. unless/if on a target
Hi,
Yes, but then I get to see *a lot* of other stuff too, which I don't want to.
There is already enough in my build log to look at ;)
Or is there may be a way to control the level of specific things such as this,
i.e. smth. like log4j's lo
Hi,
Yes, but then I get to see *a lot* of other stuff too, which I don't want to.
There is already enough in my build log to look at ;)
Or is there may be a way to control the level of specific things such as this,
i.e. smth. like log4j's logger id to control it?
tom
-Original Message
On 2010-01-18, Thomas Menzel wrote:
> Maybe I just don't know enough and this already works, but it would be
> really great if ant would tell by default that a target isn't executed
> because of an if/unless.
It does so in -verbose mode.
Stefan
-
Montag, 18. Januar 2010 13:11
To: Ant Users List
Subject: AW: ant log/output vs. unless/if on a target
Hello,
The workaround is to use antconribs task to do what "if/unless" does.
Greetings Juergen
--
Jürgen
-Ursprüngliche Nachricht-
Von: Thomas Menzel
Gesendet: Montag, 18.
Hello,
The workaround is to use antconribs task to do what "if/unless" does.
Greetings Juergen
--
Jürgen
-Ursprüngliche Nachricht-
Von: Thomas Menzel [mailto:tmen...@brox.de]
Gesendet: Montag, 18. Januar 2010 12:34
An: user@ant.apache.org
Betreff: ant log/output vs. unle
Hi,
Maybe I just don't know enough and this already works, but it would be really
great if ant would tell by default that a target isn't executed because of an
if/unless.
I just stumbled over this when I wanted to turn a target off that I'm calling
with and was wondering and debugging why the
