Refresh of module system coming to jdk9/dev soon

Alan Bateman Alan.Bateman at
Thu Dec 8 08:27:56 UTC 2016

On 08/12/2016 03:32, Martin Buchholz wrote:

> I plan to keep on using reflection to access implementation details in 
> tests, using --add-opens as necessary.  That does require having 
> control over the commandline, or using a module-aware test framework 
> that takes care of that for you (like jtreg).
That should work fine, or as I said, if the tests are compiled and run 
"as if" they are in the module being tested then they will be able to do 
deep reflective on the internal/implementation without any needed to 
open the packages.

> We still don't have a solution to the inheritDoc problem - how to 
> inherit doc comments from javadoc in superclasses in modules.
I assume you'll bring this up on javadoc-dev.

> The tools I was thinking of that might need to be jigsaw aware were 
> jol and jmh.
I assume any issues can be brought to jol-dev or jmh-dev. I recall there 
was an issue with JMH a few months ago related to how it detects the 
console encoding, I believe Claes or Aleksey has put in a fix or 
workaround for this. For JOL then it uses SA which is not an exported 
API, I believe it launches with --add-exports options to export the 
packages containing the SA classes.


More information about the jtreg-use mailing list