>Thanks Jan. Actually you're right! We're already using a build >listener to catch Ant's logs so I guess simply using a >redirector with the alwayslog attribute set to true should do >the trick. Is that correct?
Do you get the output of <java> when using "Ant alone"? Then you should get the output via your listener. What "redirector" do you mean (as Ant has <redirector>s)? >Do you know if there's any way to achieve output logging with >Ant 1.5.x? Via Ant's logging API - it's in Ant since .... mmmh .... longer than me (means more than four years) ;-) >The reason is that Cargo is a framework and while >upgrading to Ant 1.6.x is good for Cargo it's less good for >our users as they'll also need to change their dependencies. Yes, but maybe they already have a newer version. What about multiple Ant instances? Inside your framework, Ant is only a library. Jan --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
