I am soliciting opinions on the following idea: The javac tag uses the build.compiler property to determine which compiler to run. However, if you want to control the debug, optimize and deprecation options, you need to explicitly choose them in your <javac> task.
I propose a change where, instead of defaulting debug, optimize and deprecation to false, they instead obtain their initial values from optional properties named build.compiler.debug, build.compiler.optimize, and build.compiler.deprecation, and can be overridden by the defined attributes, if present. This way, you can build a debug version of your code simply by running build with -Dbuild.compiler.debug=on, instead of having to explicitly identify the debug attribute in each javac task. This seems more orthoginal to how build.compiler is used. Thanks for any comments. John
BEGIN:VCARD VERSION:2.1 N:Cocula;John;W. FN:John W. Cocula ORG:Managed Objects;Development TITLE:Founder and CTO TEL;WORK;VOICE:+1 703-208-3330 TEL;CELL;VOICE:703-930-7843 TEL;WORK;FAX:+1 703-208-3331 TEL;HOME;FAX:703-208-3331 ADR;WORK:;;7925 Westpark Drive;McLean;VA;22102 LABEL;WORK;ENCODING=QUOTED-PRINTABLE:7925 Westpark Drive=0D=0AMcLean, VA 22102 X-WAB-GENDER:2 URL:http://www.cocula.com URL:http://www.ManagedObjects.com EMAIL;PREF;INTERNET:[EMAIL PROTECTED] REV:20000509T154155Z END:VCARD
