RE: ant log/output vs. unless/if on a target

Ah, thx for pointing that out. Looking @ the docs I also found this one: Ant -logger org.apache.tools.ant.NoBannerLogger That already help a bit and my guess is that I can take it as a dev base Thx for your help tom -Original Message- From: Knuplesch, Juergen Sent: Dienstag, 19. Janua

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...@brox.de] Gesendet: Dienstag, 19. Januar 2010 08:18 An: Ant Users List Betreff: RE: ant

RE: ant 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 logger id to control it? tom -Original Message

AW: JAVA_HOME not interpreted on XP

Hello, What is your question? I always put JAVA_HOME/bin into the path variable and then it works. Greetings Juergen -- Jürgen Knuplesch -Ursprüngliche Nachricht- Von: "Stephan Müller" [mailto:stephanr.muel...@gmx.de] Gesendet: Dienstag, 19. Januar 2010 00:07 An: user@ant.apache.or

Re: ant log/output vs. unless/if on a target

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 -

JAVA_HOME not interpreted on XP

Hi list. I've run into the well known "Unable to locate tools.jar." System is XP SP3. Tested with ant-1.8.0RC1 and ant-1.6.5. Installed Java Runtime Plugin 1.4.2_04 and JDK 1.4.2_04 here're some snippets * C:\>echo %JAVA_HOME% C:\Program Files\j2sdk1.4.2_04 **

Re: I think the answer to this question is no

On Sun, Jan 17, 2010 at 11:30 PM, Mitch Gitman wrote: > Is there any programmatic mechanism within Ant to arbitrarily query what the > current log level is? [...] > > What I'd like to do is invoke getProject().log("Some message", > Project.MSG_VERBOSE) only if the current log level is verbose. No

AW: split version

You could try or the external task XmlTask http://ant.apache.org/external.html#XmlTask Jan >-Ursprüngliche Nachricht- >Von: jhoomshar...@netscape.net [mailto:jhoomshar...@netscape.net] >Gesendet: Montag, 18. Januar 2010 13:45 >An: user@ant.apache.org >Betreff: split version > > >I hav

split version

I have pom.xml, below is snippet of my pom.xml file: pom.xml --- http://maven.apache.org/POM/4.0.0"; xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"; xsi:schemaLocation="http://maven.apache.org/POM/4.0.0 http://maven.apache.org/maven-v4_0_0.xsd";> 4.0.0 com.xkri.kill.tokens tok

RE: ant log/output vs. unless/if on a target

Hi, Thx for the pointer. But since I'm using oher people's build file (eclipse PDE build) this is not an option. And even though the is quite useful there are time where if/unless are less verbose and more handy. tom -Original Message- From: Knuplesch, Juergen Sent: Montag, 18. Janua

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 [mailto:tmen...@brox.de] Gesendet: Montag, 18. Januar 2010 12:34 An: user@ant.apache.org Betreff: ant log/output vs. unless/if on a ta

ant log/output vs. unless/if on a target

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