Configurations... (Was: Re: Module-system requirements)

mark.reinhold at mark.reinhold at
Sat Feb 14 21:33:07 UTC 2015

2015/2/12 7:35 -0800, david.lloyd at
> I'm a little concerned that the configurations section implies a strict 
> hierarchy:
> "Nested dynamic configurations — An application must be able to create a 
> dynamic configuration that relates to an existing dynamic configuration 
> rather than to the application’s initial configuration."
> Why can a configuration not relate to more than one other configurations?

A tree of configurations rather than a simple linear list is more
difficult to reason about and trickier to implement (you must, e.g.,
cope with the diamond-import problem).

The feedback we've received so far has not suggested that this
limitation will be a problem in practice.  Do you have use cases
which require this flexibility?

- Mark

More information about the jpms-spec-observers mailing list