Conflicting module versions

[mark.reinhold at oracle.com]

2015/2/5 12:40 +0000, david.lloyd at redhat.com:
> I agree that working dependency resolution is a necessity for a working 
> software system.  But, it is my opinion that run time is far too late 
> for this to occur (and I intend to carry this opinion into the JSR 
> working group).  Ultimately it is up to the module distributor to ensure 
> that their distribution contains a cohesive module set.  While it is 
> possible to efficiently add certain types of validation checks at run 
> time, by this time it is far too late to do anything about a violation 
> other than just fail.

Broadly speaking, I agree.  At run time a module system should prevent
broken situations such as conflicting module versions.  It need not,
however, attempt to solve them -- that's really hard, and it generally
requires human intervention in order to identify the correct version.
Simply failing in such scenarios (with a good error message, of course)
is perfectly acceptable.

- Mark