Modules seem to be all the rage for enterprise container "app servers" and the like, but for the rest of us, modules are solving a problem that we simply don't have.
Unfortunately, a lot of third party libraries are still problematic to use in 9+, and the JVM unconditionally spits out warnings about them anyhow. So our users complain to us about problems (but not really) in code that we don't control.
It's often very easy to add a Automatic-Module-Name entry to the manifest file, and I have only had one maintainer that have been negative to it when I have opened bug in projects.
Illegal reflective access warnings are going to be a fun one to fix for unmaintained dependencies when the warnings turn to errors then turn to removals.
10
u/ObscureCulturalMeme Mar 19 '19 edited Mar 19 '19
Modules seem to be all the rage for enterprise container "app servers" and the like, but for the rest of us, modules are solving a problem that we simply don't have.
Unfortunately, a lot of third party libraries are still problematic to use in 9+, and the JVM unconditionally spits out warnings about them anyhow. So our users complain to us about problems (but not really) in code that we don't control.