2015/7/2 9:16 -0700, [email protected]:
> "We're not there yet but eventually it should be possible to run a tool
> on JDK 9 to access another JDK 9 run-time image (maybe it has a
> different set of modules) or run on JDK 9 to access a JDK 10 run-time
> image. "
>
> It's disappoint
On 03/07/2015 05:16, [email protected] wrote:
"We're not there yet but eventually it should be possible to run a
tool on JDK 9 to access another JDK 9 run-time image (maybe it has a
different set of modules) or run on JDK 9 to access a JDK 10 run-time
image. "
It's disappointing
[email protected] wrote:
The JEP says that the module container format is
"implementation-specific" and "subject to change without notice". My
concern is that this is going to end up screwing over tool
maintainers, such as myself. I maintain an opensource tool th
On 02/07/2015 20:01, [email protected] wrote:
The JEP says that the module container format is
"implementation-specific" and "subject to change without notice". My
concern is that this is going to end up screwing over tool
maintainers, such as myself. I maintai
The JEP says that the module container format is
"implementation-specific" and "subject to change without notice". My
concern is that this is going to end up screwing over tool maintainers,
such as myself. I maintain an opensource tool that scans through core
Java classes
