[jsr294-modularity-eg] Ignoring unknown directives...

[Bob Lee]

On Wed, Jun 24, 2009 at 1:40 PM, Bryan Atsatt <bryan.atsatt at oracle.com>wrote:

>  We are talking about locating a single implementation object (i.e. a
> ModuleSystem subtype) that can both validate the contents of a ModuleInfo as
> well as provide resolution based on it. While we could potentially split
> validation across multiple such objects, the compiler can't be responsible
> for combining multiple resolution results into a single one. So it seems
> reasonable to simply require any system that combines runtimes, layered or
> not, to provide a single, combined implementation. In your example, that
> implementation would have to combine logic for both OSGi and Guice.
>

Of course, using annotation-like module directive types addresses all of
these problems and enables some level of validation by the compiler even
when the module system can't perform higher-level validations (simple
misspellings won't just be ignored, for example). It also feels a lot more
like Java. ;-)

Bob
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://cs.oswego.edu/pipermail/jsr294-modularity-eg/attachments/20090624/9fb08091/attachment-0001.html>