The MANIFEST.MF in a jar must be at the first or second position. The second position is valid iff the first position is the META-INF directory. It seems classgraph 4.8.56 is the last one that has this correct. I assume that 4797249 is the cause of this problem.
The result is that any jar tool and any jar based logic in the jdks is unable to find the manifest and its folder properly. Because the folder is not found properly the jar is not recognized as proper module, leading to a different module name and messing the build up when using the jigsaw multi module feature in gradle 6.4-rc1.
See for example Zlika/reproducible-build-maven-plugin#16 for a discussion about the positioning.
The MANIFEST.MF in a jar must be at the first or second position. The second position is valid iff the first position is the META-INF directory. It seems classgraph 4.8.56 is the last one that has this correct. I assume that 4797249 is the cause of this problem.
The result is that any jar tool and any jar based logic in the jdks is unable to find the manifest and its folder properly. Because the folder is not found properly the jar is not recognized as proper module, leading to a different module name and messing the build up when using the jigsaw multi module feature in gradle 6.4-rc1.
See for example Zlika/reproducible-build-maven-plugin#16 for a discussion about the positioning.