Define modules top-down to avoid constraints?

[Alan Bateman]

Mandy,

I've been playing around further with the tool. The main observation is 
that many of the possible fine-grain modules are awkward to configure 
because they need several constraints to prevent them pulling in the 
world. The configuration is also fragile as it is very sensitive to 
ordering. For these "simple modules" it might be easier to define them 
top-down. In other words, they are configured by matching classes in the 
configuration without the dependency analysis. We still need the 
dependency analysis of course (esp. for the initial land-grab by base). 
Here's the webrev with the changes:
   http://cr.openjdk.java.net/~alanb/jigsaw-tools/webrev.00/

In summary it adds a "contents" key to list the classes to include. It 
works with "exclude" so the list can be filtered.  The webrev also has 
fixes to a few issues that I ran into when running without the catch-all 
"other" configuration.  The webrev also has many of the module 
configuration files that I've been using.  If they seem reasonable then 
I can include the changes to the script to use them. Just on that, I 
find that my list of parameters takes several lines so we might think 
about allowing multiple modules to be configured in the same file.

-Alan.