My understanding (from JEP 220) is that these run-time images are created
specifically for the JDK/JRE and the IDE is only expected to read these.
User defined modules will either be in source form or JAR form. One of the
goals of the JEP 220 is this:
"Restructure the JDK and JRE run-time images to draw a clear distinction
between files that developers, deployers, and end-users can rely upon and,
when appropriate, modify, in contrast to files that are internal to the
implementation and subject to change without notice. "
The way I see it, a Jimage is purely meant to be part of a JDK and nowhere
else.
Regards,
Jay
From: Mike Milinkovich <[email protected]>
To: Daniel Megert <[email protected]>, Cross project issues
<[email protected]>
Date: 10/28/2015 02:49 AM
Subject: Re: [cross-project-issues-dev] Announcing JDK 9 support for
Eclipse Neon
Sent by: [email protected]
On 27/10/2015 5:18 PM, Daniel Megert wrote:
> "Instead, API is provided for reading the content of such image."
==> The format is not specified but APIs allow to read the content.
Maybe I am wrong, but since we are a Java IDE don't we also have to *write*
the content of such files?
--
Mike Milinkovich
[email protected]
+1.613.220.3223 (mobile)
EclipseCon
Europe 2015
_______________________________________________
cross-project-issues-dev mailing list
[email protected]
To change your delivery options, retrieve your password, or unsubscribe
from this list, visit
https://dev.eclipse.org/mailman/listinfo/cross-project-issues-dev_______________________________________________
cross-project-issues-dev mailing list
[email protected]
To change your delivery options, retrieve your password, or unsubscribe from
this list, visit
https://dev.eclipse.org/mailman/listinfo/cross-project-issues-dev
