Modules merging support in ClassAnalyzer

[Mark Reinhold]

> Date: Fri, 30 Oct 2009 11:50:47 +0000
> From: alan.bateman at sun.com

> Mark Reinhold wrote:
>> In concrete terms:
>> 
>>   module jdbc-base
>>   include java.sql.*
>> 
>>   module jdbc-enterprise
>>   include javax.sql.XA* javax.sql.rowset.**
>> 
>>   module jdbc
>>   include jdbc-base jdbc-enterprise
>> 
>> This would generate just jdbc.{classlist,dependencies,summary}.
>> 
> Should we be using a naming convention to make this easier? I note, for
> example, that we currently have "rmi" and "rmi-activation" for analysis
> purposes and maybe the fine-grain "rmi" should be something like "rmi-base" to
> avoid a conflict with a coarser-grain "rmi" module. "jndi" is another example,
> and maybe this should be "jndi-api" or "jndi-framework".

Yes, I think that makes sense.  We should prefer simple names (without
dashes or other punctuation) for the (emerging) coarse-grained modules,
and use a prefix-suffix convention for the fine-grained cases.

- Mark