Name driver modules using Automatic-Module-Name

XMLWordPrintableJSON

    • Type: Improvement
    • Resolution: Fixed
    • Priority: Major - P3
    • 3.7.0
    • Affects Version/s: None
    • Component/s: Packaging
    • None
    • None
    • None
    • None
    • None
    • None
    • None
    • None

      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.

            Assignee:
            Jeffrey Yemin
            Reporter:
            Jeffrey Yemin
            None
            Votes:
            0 Vote for this issue
            Watchers:
            1 Start watching this issue

              Created:
              Updated:
              Resolved: