Glenn kindly notified me of a bug in our VAJ PlugIn: > Trapping System.out - this really should be fixed, but its up to you. If > you are getting output in a window, you don't expect chunks of pertinent > output to show up on the console. People don't write <echo> tasks if they > don't want to see output. If you don't fix it, I'd put a big warning in > the docs. >
After having thought about this a little, I'm wondering if it's not the echo task that should be fixed :-). It seems to be the only task that does not use the BuildLogger mechanism for output. The descriptions says "Echoes a message to System.out", but that is a description from the implementers point of view, not the users. I as user would like the echo output behave as the outputs of all other tasks (i.e. going to all registered BuildLoggers), but I'm not sure if this is true for all other Ant users, too. Is there any reason for this special behaviour (besides historical reasons)? I see an additional advantage when we change the Echo task to log its output: We could introduce a new "ouputLevel" property to control, at which logging levels that message is displayed (default would be 'always', but we could introduce 'warning', 'info' and 'verbose', too). Wolf
