Updated for NetBeans 12: Using the Netbeans IDE to work on JDK library development

Bradford Wetmore bradford.wetmore at oracle.com
Sat Jun 13 01:06:09 UTC 2020

On 6/11/2020 6:30 PM, Weijun Wang wrote:
>> 1.  Build a JDK to debug.  Exploded is the fastest to build/debug.
> Then why not suggest --with-default-make-target=exploded-image below?

jdk is just an alias for exploded-image AFAIK.  The main thing to avoid 
is images!  :)

AFAIK, you will need to set the configure --with-default-make-target, 
otherwise, the default will be images.

% make help
Common make targets
  make [default]   # Compile all modules and create a runnable "exploded"
                   # image (alias for jdk or exploded-image)

>>     % bash configure \
>>           --with-default-make-target=jdk ...other options...
>> 6b.  JTREG:  In the java.base module you opened (above), navigate to the jdk test tests in the following directory entry:
>>     ${jdkRoot}/test/jdk     # ${jdkRoot}/open/test/jdk/ if using closed
>> Then select the exact test you want to run, then "Debug->Debug Test File".
>> NOTE WELL:  The JTReg plugin understands the JTReg directives. Debugging a JTReg test used to trigger a remake of the entire(!) JDK. Turn this behavior off by right clicking on the java.base module, then "properties", then set "Never" to the question of "Build before running tests."  I *THINK* NB 12 no longer does a rebuild, but in case you don't and you end up with a long delay, this might be the problem.
> Still "always" by default.

Agreed that it shows as "always", but when I tried to debug a test file 
(and quickly slapped my forehead for forgetting to turn it to "never"), 
it started up pretty quickly, so maybe it no longer does this?

> Do you know if there is a way to configure jtreg options. For example, I want -nr to avoid test report.

Don't know offhand.  Jan Lahoda might be your best resource.


More information about the jdk-dev mailing list