On Thu, 21 Mar 2002 19:42, Adam Murdoch wrote: > > -----Original Message----- > > From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] > > > > > > /** > > * Printout all the properties in ant runtime. > > */ > > public void execute() > > { > > final Map properties = getContext().getProperties(); > > final Iterator iterator = properties.keySet().iterator(); > > while( iterator.hasNext() ) > > { > > final String key = (String)iterator.next(); > > final Object value = properties.get( key ); > > getContext().warn( key + "=" + value ); > > } > > } > > I wonder whether it's time for a new log level. It strikes me as kinda odd > that we have to use warn() rather than info() to write info messages that > we want to appear when not running --verbose. We probably want to pull > info() and warn() up, and add a verbose() or verboseInfo() between debug() > and info(). > > Thoughts? How is this going to work with Logger? >
Yep, I definitely think it's strange behaviour that at the default log level, you get almost no feedback. I was going to suggest making "info" the default level. I hadn't thought that warn() should be used for regular feedback - just doesn't feel right. I suppose having another level between info and debug would be helpful, because in many cases you want to provide optional extra info for *BuildFile* writers, without spewing out the entire debug info. (Debug can then be kept for incredibly verbose output that helps *Task* developers track down bugs). ciao Daz -- To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]> For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>
