On 08/08/2016 17:34, Steve Drach wrote:
:
Back to the old drawing board ;-)
I think we can do this in phases, starting out with jlink picking up the
runtime version and using that to select the resources from the modular
JAR would be a good start. At some point we will have an update module
path implementation that better supports link time, in which case you
can find java.base and then use its version (as opposed to the runtime
version) when finding modules.
:
The issue has to do with multi-release jar files. How do exploded images
relate to multi-release jar files.
If you look at the other jlink tests then you'll see that they skip
silently when on an exploded image (no packaged modules, meaning no JMOD
files).
-Alan
