[jsr294-modularity-eg] 294 EG conf call, 2009-06-17

[BJ Hargrave]

> There would be at most one directive for identifying the module system 
> allowed. BJ pointed out that bundles often have a manifest which uses 
> OSGi-spec headers and Eclipse-custom headers, and so require more than 
> the 'standard' OSGi module system. The analogue in module-info.java is 
> writing (something like) 'system osgi+eclipse'. If a programmer really 
> wants to write a module resolvable in radically different module 
> systems, then they'd write (something like) 'system osgi/jigsaw' and it 
> would be up to a module system facade to interpret that.

I also was concerned about there being no ordering implications. That is 
osgi+eclipse is identical to eclipse+osgi. In that light, it seems that 
comma (',') would be a better separator of the set members: 'system 
osgi,eclipse,guice'.
-- 

BJ Hargrave
Senior Technical Staff Member, IBM
OSGi Fellow and CTO of the OSGi Alliance
hargrave at us.ibm.com

office: +1 386 848 1781
mobile: +1 386 848 3788
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://cs.oswego.edu/pipermail/jsr294-modularity-observer/attachments/20090624/7a11d510/attachment.html>
-------------- next part --------------
_______________________________________________
jsr294-modularity-eg mailing list
jsr294-modularity-eg at cs.oswego.edu
http://cs.oswego.edu/mailman/listinfo/jsr294-modularity-eg