On Wed, 25 Jul 2001 00:57, Stefan Bodewig wrote: > > I see ant2 as having subloggers for stdout and stderr. So if a task > > wanted to massage its output (like junit task or whatever) it could > > just register a listener at correct location in logger > > hierarchy. > > And prevent output from going to the default logger as well or send it > there in addition to the task specific logging?
Both are possible. By default both LogKit and Log4j will inherit parents output destination unless explicitly set. If you explicitly set them then it overides. However both toolkits allow possibility of of adding an extra listener for output (Log4j directly by additivity and LogKit indirectly by giving access to LogTarget array). > I've split feelings about replacing default loggers - as some tasks do > in effect right now. Of course, the tasks that do it ATM, do so on > user request (out parameters or the formatter stuff in the junit > task). > > An approach like this could also be used as an aspect that replaces > the the out attributes of <java> and <exec>, yes, I think I like it as > well. Kewl .. now we just gotta find a nice way of dealing with standard input ;) Cheers, Pete *-----------------------------------------------------* | "Faced with the choice between changing one's mind, | | and proving that there is no need to do so - almost | | everyone gets busy on the proof." | | - John Kenneth Galbraith | *-----------------------------------------------------*
