----- Original Message ----- From: "Joseph Dane" <[EMAIL PROTECTED]> To: "Ant Developers List" <[EMAIL PROTECTED]> Sent: Tuesday, November 05, 2002 12:15 PM Subject: Re: Request: Change <javac> debug default to "on"
> But I should probably ask: why was the decision originally made to > make the default "no-debug"? you have to go back through the annals of CVS to find out. ... DefaultCompilerAdapter patch 1.4 on 2001-03-28 fixed Bug #1011 If debug is set to false pass -g:none to javac if JDK 1.2 or JDK 1.3 to get really no debug information at all. ----- debug=false has been the way it was since the CVS repository existed, so that's a 'dont know'. I'd assume because the tomcat team were writing a tool to build tomcat, not a generic dev tool. Looking at command javac.exe, the default there is not -g , give out everything, but -g: source and lines. Prior to bug#1011 being fixed (which meant ant never ever generated files without some debug), ant defaulted to always generating some debug info, probably lines and source. It did this by not saying anything to javac and taking its defaults. So...up to ant1.3 the situation was debug=false was the default, but you really got -g:lines,source in ant1.4 you got debug=false was the default, and you really got -g:none in ant1.5 we got debug=false was the default, but you could select which options to debug. When you set debug=true the default was -g:source,lines,vars So if people are trying to fix things to be compatible with javac and backwards compatible, they come up with a system that -defaults to -g: source,lines -when debug=false really generates nothing -when debug=true really generates everything Plus the tests to verify it. You can use commons-discovery to look at the debug info. -- To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]> For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>
