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.

Bug 94377 - More control over debug level when compiling Java sources
Summary: More control over debug level when compiling Java sources
Status: NEW
Alias: None
Product: java
Classification: Unclassified
Component: Project (show other bugs)
Version: 6.x
Hardware: All All
: P2 blocker (vote)
Assignee: Tomas Zezula
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2007-02-05 13:44 UTC by _ rkubacki
Modified: 2011-12-19 19:25 UTC (History)
1 user (show)

See Also:
Issue Type: ENHANCEMENT
Exception Reporter:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description _ rkubacki 2007-02-05 13:44:50 UTC
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.
Comment 1 mslama 2007-03-22 16:18:50 UTC
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?
Comment 2 mslama 2007-03-22 16:29:50 UTC
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.
Comment 3 jla 2011-12-19 19:25:57 UTC
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.