Automatic module names
David M. Lloyd
david.lloyd at redhat.com
Tue Feb 7 14:03:38 UTC 2017
On 02/06/2017 12:51 PM, Alan Bateman wrote:
> On 06/02/2017 18:25, David M. Lloyd wrote:
>> I don't think there is really a substantial increase in risk between
>> manually modularizing a library and relying on automatic modules.
> If several projects take on the responsibility to modularize a library
> that they don't maintain then there is no guarantee that they will end
> up with equivalent modules. Static analysis (`jdeps
> --generate-module-info ...`) gets you so far but it often needs a deeper
> understanding of the library to be confident that the module declaration
> that they write for the library is complete. Automatic modules take on
> much of the behavior of a library on the class path so that it's not
> necessary to synthesize everything that an explicit module would declare.
As could a tool, which has the added advantage that the module
information could easily be incrementally narrowed instead of going
fully from automatic to fully specified. To do incremental change from
automatic to fully specified, you'd need a tool to generate an
automatic-equivalent descriptor anyway.
More information about the jigsaw-dev