Framework changes

[Richard S. Hall]

Hello everyone,

I just committed some reasonably big changes to the framework in 
preparation for support for require-bundle. In short, the module loader 
abstraction previously worked in terms of exports/imports, but now it 
has been generalized to work in terms of capabilities/requirements. A 
capability is simply a set of properties, while a requirement is a 
filter over a set of properties.

The idea is that this generalization will simplify adding different 
types of constraints to the framework's resolver algorithm. So, this 
first step simply converts exports/imports to capabilities/requirements, 
while the next step will be to introduce bundle 
capabilities/requirements. Work will start on this second step shortly.

I am making these changes directly in the trunk and have run the current 
set against the TCK. Preliminary results appear to indicate that I 
haven't broken anything, but you never know. Please be on the look out 
for any strange behavior and report back to the list if you think 
something has gone amiss.

Thanks.

-> richard