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

Weijun Wang weijun.wang at oracle.com
Fri Jun 12 01:30:06 UTC 2020

> 1.  Build a JDK to debug.  Exploded is the fastest to build/debug.

Then why not suggest --with-default-make-target=exploded-image below?

>    % 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.

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


More information about the jdk-dev mailing list