Hi Andrei,
I will look at your contribution. Didn’t you add the same issue twice?
Thanks.
JF
On 6 Oct 2015, at 19:35, Andrei Eremeev wrote:
> Resending. I am covered by the OCA; so I can contribute to OpenJDK.
>
> Best regards,
> Andrei Eremeev
>
> Tuesday, October
Thanks!
This looks much better than I naively expected, especially w.r.t.
footprint, and I probably wouldn't have asked/suggested what I did if
I'd gotten the attachement the first time around (although I'd prefer
some native memory measurement over "heap-after-GC", this should be
indicative
Yes, the message says that "JDevJavaCompiler ... cannot access ...
com.sun.tools.javac.api.JavacTool"
and indeed, com.sun.tools.javac.api is not a supported public API.
Here's the standard comment from the head of the file:
* This is NOT part of any supported API.
* If you write code that
It is possible in JDK8 and before to run JSR199 compilations using a
class loader that loads from tools.jar. I can't do something similar in
JDK9 using a new jigsaw build, trying to load from jrt-fs.jar. I get
this: Warning: Cannot use jsr199 Javac from jrt-fs.jar".
Does this mean you can
On 10/07/2015 06:01 PM, Keimpe Bronkhorst wrote:
The underlying exception I get is:
"Class oracle.jdevimpl.javacompiler.JDevJavaCompiler can not access a
member of class com.sun.tools.javac.api.JavacTool (module
jdk.compiler) with modifiers "public static", module jdk.compiler does
not
The underlying exception I get is:
"Class oracle.jdevimpl.javacompiler.JDevJavaCompiler can not access a
member of class com.sun.tools.javac.api.JavacTool (module jdk.compiler)
with modifiers "public static", module jdk.compiler does not export
com.sun.tools.javac.api to "
Will there be a