Stuck on an issue?

Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.

And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.

Java Modules

See original GitHub issue

Looks like I can’t use your module with a module-info, I think it’s missing either an Automatic-Module name or whatever in MANIFEST.mf, although at this point it might be better to just add the module-info.java

Issue Analytics

State:
Created 2 years ago
Reactions:1
Comments:5 (2 by maintainers)

Top GitHub Comments

1reaction

xenoterracidecommented, Jul 4, 2021

The module descriptor for an automatic module does not declare any dependences (except for the mandatory dependency on java.base), and does not declare any exported or open packages. Automatic module receive special treatment during resolution so that they read all other modules in the configuration. When an automatic module is instantiated in the Java virtual machine then it reads every unnamed module and is treated as if all packages are exported and open.

just means that certain forms of classpath scanning might be a little less efficient I guess… I’m not going to pretend to fully understand all implications.

0reactions

xenoterracidecommented, Jul 5, 2021

I’m not 100% certain, but if you do, you may have to either split build artifacts with jdk 11+ using -release, or just create a new major version that requires java9+. I could be totally wrong about that though, best to test.