DO NOT REPLY [Bug 35234] - Make the javah task fall back to executing javahMake javah task fall back to executing javah command

DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG· RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT . ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND· INSERTED IN THE BUG DATABASE. http://issues.apache.org/bugzilla/show_bu

DO NOT REPLY [Bug 39617] - The task should have an append attribute

DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG· RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT . ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND· INSERTED IN THE BUG DATABASE. http://issues.apache.org/bugzilla/show_bu

tracing macros?

Hey, I'm using macrodef a lot (a really great feature). What I'm looking for is a simple way of tracing which macro is invoked. Something like "entring macro .. ", "leaving macro ..". So derived a Trace class from org.apache.tools.ant.taskdefs.Sequential, some- thing like: public class Tra

Re: per-task diagnostics

Jeffrey E Care wrote: I know I'm a little late to this party - I've been tied up in my new assignment. Anyway, FWIW here's my opinion: I've been thinking about how we could improve our diagnostics, by moving more of the diags into tasks themselves. Every task could have a diagnostics(PrintS

Re: per-task diagnostics

I know I'm a little late to this party - I've been tied up in my new assignment. Anyway, FWIW here's my opinion: > I've been thinking about how we could improve our diagnostics, by moving > more of the diags into tasks themselves. Every task could have a > diagnostics(PrintStream) method that