On 07/04/2016 12:25, Dawid Weiss wrote:
Tried again, it works. By the way -- jar's help says upgrademodulepath
are directories, it's useful to know they can be exact file pointers
too.
-upgrademodulepath <module path>...
A ; separated list of directories, each directory
is a directory of modules that replace upgradeable
modules in the runtime image
That is java usage output but you are right, it wasn't updated. We'll
get that fixed.
:
I did. But I also wanted some sanity check so I opened
java.annotations.common.jmod and copied everything from classes/* to
another zip file (java.annotations.common.jar). I notice there are sha
checksums inside module-info.class, but these files are identical and
they still produce the same error:
Error occurred during initialization of VM
java.lang.module.ResolutionException: Unable to compute the hash of
module java.base
Probably the hashes are computed based on something else than file
content alone (?).
The hashes are computed from the packaged modules (JMODs or modular
JARs). The "Unable to compute ..." here is because the hashes checked at
link time but aren't saved in the runtime image. There is a big refresh
of the integrity checks come that will clean this up.
-Alan.
