[JAVA-2706] Name driver modules using Automatic-Module-Name Created: 14/Dec/17 Updated: 28/Oct/23 Resolved: 10/Jan/18 |
|
| Status: | Closed |
| Project: | Java Driver |
| Component/s: | Packaging |
| Affects Version/s: | None |
| Fix Version/s: | 3.7.0 |
| Type: | Improvement | Priority: | Major - P3 |
| Reporter: | Jeffrey Yemin | Assignee: | Jeffrey Yemin |
| Resolution: | Fixed | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Epic Link: | Java9 |
| Description |
|
Until all the driver's dependencies commit to names for their respective modules, the driver can not safely create a module-info.jar file that requires those modules. Currently the driver depends on SLF4J and Netty, and neither have yet released with module names (though SLF4J has a beta that is modularized). But we can still make progress and help the community by adding an Automatic-Module-Name entry to the manifest for each jar file. This commits the driver to a set of module names that downstream dependencies can rely on when defining their own modules, and once the driver's dependencies have done the same, we can consider adding module-info.java into the mix. |
| Comments |
| Comment by Githook User [ 09/Jan/18 ] |
|
Author: {'email': 'jeff.yemin@10gen.com', 'name': 'Jeff Yemin', 'username': 'jyemin'}Message: See https://docs.oracle.com/javase/9/docs/specs/jar/jar.html#Modular |