The critical missing pieces and a path forward
David M. Lloyd
david.lloyd at redhat.com
Wed May 10 22:24:46 UTC 2017
On 05/09/2017 07:49 AM, David M. Lloyd wrote:
> On 05/08/2017 09:57 AM, mark.reinhold at oracle.com wrote:
>> This module system loads application modules into a single class loader
>> by default so that developers have one less behavioral difference to
>> worry about as they upgrade their components to explicit modules. An
>> early prototype did load every module into its own loader by default.
> What about a command line option to either opt in to or opt out of
> having separated class loaders? The class loader of each module in this
> case should be able to resolve only the same set of types and resources
> that its corresponding module does. This way, users can use the module
> path without custom code, while still being able to take advantage of
> more advanced use cases.
> Ideally jlink would also support such an option.
As time passes since the vote, it is becoming clear that at least some
of the "no" votes were cast in whole or in part because isolating
package namespaces within modules is indeed considered a fundamental
expectation of a module system's capabilities. Please give this idea
More information about the jpms-spec-observers