The unnamed module
Well, we weren't wrong. All code in Java 9 needs to be in modules. And all modules need to have the right readability and accessibility relationships for applications to work. But that might be problematic! Because, as with every new Java release, there are thousands of developers trying to run their legacy Java code bases using the new Java version. If we were to expect each legacy Java code base to be wrapped into modules before it can even run in Java 9, which would introduce a significant cost of effort in the developer community. Thankfully, there's a way out. When you are using Java 9 to compile or run legacy module-less Java code in the classpath, you don't have to manually create module wrappers yourself. The platform ...
Become an O’Reilly member and get unlimited access to this title plus top books and audiobooks from O’Reilly and nearly 200 top publishers, thousands of courses curated by job role, 150+ live events each month,
and much more.
Read now
Unlock full access