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

[Paul Benedict]

For the record, I am against the idea of having different
module-info.java files per module type. I want to build one bundle
that can be used in multiple module systems. The only configuration
idea that appears analogous to this need is CSS media selectors:

@media screen {
    selector1 {...}
    selector2 {...}
}

@media print {
    selector1 {...}
    selector2 {...}
}

Why couldn't JSR-294 do the same? This is just a rough example to digest:

// Meant to be consumed by all modules
module @ system {
  requires module m:1.1 local;
  requires module n:1.0 vendor=Sun optional;
}

// OSGI specific requirements
module @ osgi {
  permits foo:1.0;
  permits bar vendor=Sun;
  classpath a.jar b.jar c.jar;
}

// Guice specific requirements
module @ guice {
  permits foo:1.0;
  permits bar vendor=Sun;
  classpath a.jar b.jar c.jar;
}