This Bugzilla instance is a read-only archive of historic NetBeans bug reports. To report a bug in NetBeans please follow the project's instructions for reporting issues.
Currently it is possible to turn on/off generating debug information but it would be nice to get finer granularity and have also possibility to specify what debug information are generated. I mean not only use <javac ... debug="${javac.debug} ... to perform compilation but add more: <javac ... debug="${javac.debug} debuglevel="${build.compiler.debuglevel}" ... defaulting to "lines,vars,source" (http://ant.apache.org/manual/CoreTasks/javac.html). For me it is enough to specify required level in .properties file for given project and don't need UI.
Main reason for this is that default javac debug level is lines,source but we now support only -g:none or -g which means full debug info. Simple addition of new parameter eg. javac.debuglevel into macro javac would be enough. Then it would set desired debug level together with javac.debug=true. It is the same way as javac ant task does. No need to invent wheel. Is there any workaround till it is implemented?
It is not about UI ie. UI can stay as it is and has the same effect as now. As in ant javac task debuglevel value should be ignored if debug is false.
I think this is already fixed. My 7.0/harness/common.xml references these variables and harness/README lists them under properties which may be defined in your project.properties: <nb-javac ... debug="${build.compiler.debug}" debuglevel="${build.compiler.debuglevel}"...> build.compiler.debug - default "true" to include debugging info when compiling (needed if you want to step through sources). build.compiler.debuglevel - default "source,lines,vars" to include all debugging info.