Using an IDE to work on the Java library

[Bradford Wetmore]

>>> I suspect the problem is that the sources of the jdk.internal.vm.ci
>>> module (and a few other modules) are not in the package hierarchy under
>>> share/classes. I.e., there is no
>>> src/jdk.internal.vm.ci/share/classes/jdk/vm/ci/code (as there is
>>> src/java.base/share/classes/java/lang). There is only
>>> src/jdk.internal.vm.ci/share/classes/jdk.vm.ci.code/src/jdk/vm/ci/code,
>>> but the (module) source path is referring to src/*/share/classes, not to
>>> src/*/share/classes/jdk.vm.ci.code/src. I suspect this needs some
>>> workarounds in IDE projects, as there are workarounds in the build
>>> system for this. I don't think anyone was using the project for these
>>> modules so far (the project is working OK for me for java.compiler,
>>> jdk.compiler, java.base, jdk.jshell and occasionally java.desktop). I'll
>>> see what can be done.
>>
>> That would be awesome!  The last few days I've been trying to work on
> 
> There should be an updated version of of the plugin available now. 
> Should be possible to open src/jdk.internal.vm.ci/ as a project, set 
> breakpoints in the source files, and when debugging, debugger should be 
> able to stop there (I was able to only do limited testing, though).

Just FYI, I was able to open the jdk.internal.vm.ci module using Jan's 
updated plugin, and could at least see under 
${basedir}/share/classes/jdk.vm.ci.common/src, that there is a package 
jdk.vm.ci.common with the file JVMCIError.java.

I was able to tag a breakpoint, but didn't actually try anything that 
would test it.  (screenshot on request :) )

Good luck,

Brad