[jsr294-modularity-eg] API updates...
peter.kriens at aqute.biz
Thu Jul 16 04:23:54 EDT 2009
From my experience: less is more. So anything that isn't absolutely
necessary to interoperate should be left out.
On 16 jul 2009, at 02:01, Doug Lea wrote:
> Bryan Atsatt wrote:
>> I've taken the liberty of pulling-together/refactoring the set of
>> API classes I think we need to work with the proposed language/vm/
>> classfile changes.
> I wonder just how much of this must be standardized
> beyond interface ModuleSystem (in addition to Alex's posted
> RuntimeModule etc.) Since ModuleSystem itself can be bootstrapped
> by other means, there is not a whole lot you absolutely need
> standardized to get one going. Would people (OSGi and Jigsaw folks
> in particular) be happier leaving most of this out and targetting
> eventual standardization for some later JSR?
> jsr294-modularity-eg mailing list
> jsr294-modularity-eg at cs.oswego.edu
jsr294-modularity-eg mailing list
jsr294-modularity-eg at cs.oswego.edu
More information about the jsr294-modularity-observer