If you want more specific: <echo> supports multiple loglevel. - LogLevel defined with nested class extending EnumeratedAttribute => Ant will enforce that only valid values are set - setLevel(LogLevel) uses cascading if-statements for evaluating the value if ("debug".equals(loglevel.getValue())) ...
Jan > -----Ursprüngliche Nachricht----- > Von: Harsha Kalidindi [mailto:[EMAIL PROTECTED] > Gesendet am: Dienstag, 6. Mai 2003 19:13 > An: Ant Developers List; Ant Developers List > Betreff: Re: AW: command line option visibility within a task .. > > Peter: > > Thanks for the example. > > I was thinking of an attribute called debug for my > tasks but I > think I will use verbose to keep it consistent .. > > Regards, > Harsha > > > > >The normal way is get debug output is to > >use log(..., Project.MSG_VERBOSE); > > > >And then use -debug at the command line. > > > >This however results in a lot of debug output.... > > > >So some tasks have a verbose attribute - like for <delete/> > ><delete vebose="${delete.verbose}" ...> > > > >ant -Ddelete.verbose="yes" ... > > > >Check the source (ant.apache.tools.ant.taskdefs.Delete) for > example code. > >Peter > > > >On Tuesday 06 May 2003 17:52, Harsha Kalidindi wrote: > > > Jan,Peter: > > > > > > Thanks for fixing the email address. > > > > > > >Main.main() -> Main.start() -> Main.Main() and none of > these methods > > > >store the arguments. So you can´t access them. > > > >You can modify this class (should be very easy ...). But > then you have a > > > >customized version of an Ant base class. > > > > > > I definitely don't want to customize a base Ant class .. > > > > > > I'll have to think about this .. > > > > > > Regards, > > > Harsha > > > > > > > > -----Ursprüngliche Nachricht----- > > > > > Von: Harsha Kalidindi > [mailto:[EMAIL PROTECTED] > > > > > Gesendet am: Dienstag, 6. Mai 2003 18:11 > > > > > An: [EMAIL PROTECTED] > > > > > Betreff: command line option visibility within a task .. > > > > > > > > > > Hi: > > > > > > > > > > I am trying to write a few tasks to extend ant in > > > > > our environment. > > > > > > > > > > I would like these tasks to emit some debug > > > > > information depending > > > > > on the command line options used with the ant invocation. > > > > > > > > > > Is there a way I can get a list of command line > > > > > options that ant > > > > > was invoked with? > > > > > > > > > > Thanks, > > > > > Harsha > > > > > > > > > > [EMAIL PROTECTED] 212.762.4165 > > > > > > > > > > This communication is intended for the addressee(s) > and may contain > > > > > confidential and legally privileged information. We > do not waive > > > > > confidentiality or privilege by mis-transmission. If you have > > > > > received this > > > > > communication in error, any use, dissemination, printing or > > > > > copying is > > > > > strictly prohibited; please destroy all electronic and paper > > > > > copies and > > > > > notify the sender immediately. > > > > > > [EMAIL PROTECTED] 212.762.4165 > > > > > > This communication is intended for the addressee(s) and > may contain > > > confidential and legally privileged information. We do not waive > > > confidentiality or privilege by mis-transmission. If you > have received this > > > communication in error, any use, dissemination, printing > or copying is > > > strictly prohibited; please destroy all electronic and > paper copies and > > > notify the sender immediately. > > > > > >--------------------------------------------------------------------- > >To unsubscribe, e-mail: [EMAIL PROTECTED] > >For additional commands, e-mail: [EMAIL PROTECTED] > > [EMAIL PROTECTED] 212.762.4165 > > This communication is intended for the addressee(s) and may contain > confidential and legally privileged information. We do not waive > confidentiality or privilege by mis-transmission. If you have > received this > communication in error, any use, dissemination, printing or > copying is > strictly prohibited; please destroy all electronic and paper > copies and > notify the sender immediately. >