On 19/10/2015 18:41, Uwe Schindler wrote:
Hi,
As a tool developer (in my case it's the "forbidden-apis" tool [*], used to
disallow certain API signatures in compiled code), it would also be good to allow
differentiating between real JDK runtime modules (those that are public and part of the
JDK) from those which are 3rd party plugins maybe linked into the runtime image, but that
are not part of the official JDK / Java spec.
If this is already possible it would be good to find out how to do this. Currently I look at module
name and check that it starts with "java." (like "java.base")
Uwe
[*] https://github.com/policeman-tools/forbidden-apis
JEP 200 [1] proposes that standard/JCP-governed modules have names
starting with "java." and that JDK-specific modules start with "jdk.".
So yes, looking at the module name seems right here.
-Alan
[1] http://openjdk.java.net/jeps/200
