Rafael Winterhalter

No, I have no opportunity to reproduce this problem. Did you try logging of class loading?

Are you using a random naming strategy? Likely, some byte code is changed during prerun and compile?

I assume that there is still some randomness and hash `07e29f719685ecf5d1653a0` is not part of the generation. Could you check the generated JSON file for what hash is recorded? Can...

The plugin to generate the module-info works as expected, but indeed, ASM does not reproduce the packages that are provided to it when reading the generated module-info. I will look...

It seems like the `ModulePackages` attribute disappears somewhere during jar file packaging. It is generated correctly. But if I unzip the jar and check the contained `module-info`, it seems to...

This seems to be related to the "jar" tool. With Java 8, everything works. The `module-info` class file is simply included as is. With Java 17 or 21, the `ModulePackages`...

This seems to be related to the "jar" tool. With Java 8, everything works. The `module-info` class file is simply included as is. With Java 17 or 21, the `ModulePackages`...

Turns out that the jar tool processes the package attribute of a module-info when placing it in a jar and removes all packages that are not contained. This breaks here...

Can you try master now?

Java 17 does not validate this aspect of a module info. Seems like that code was introduced in Java 20 and not backported.