Reserving library names
Let's say you are a library developer who is not ready to migrate your code to Java 9 yet. We know that's not a problem. Other Java 9 applications can still consume your library by dropping the JAR into the module path, thus making an automatic module out of it. They use the auto-generated module name from the JAR file name and use that in their module definition files. However, what if you have a really cool name for your module that you plan to use when you eventually get to migrating to Java 9? Does it mean that all the consumers will then have to go to all the module definitions that specify the auto-generated name and update them to the new module name? That can be tedious.
The Java 9 platform gives library authors ...
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