Adrian Brock wrote:
So a 291 module that hasn't been updated to reflect changes from 294
would just expose package exports and the importing 277 module
would know how to deal with that?
A 291 module which exports packages is fundamentally exporting public
types, which will continue to work acr
On Tue, 2008-06-10 at 17:10 -0700, Stanley M. Ho wrote:
> > ModuleDefinition still refers to exported and member classes.
> > Although this is probably more of an issue for 294/291 interoperation,
> > I don't think 291 has such notions?
>
> With modules in the language, only public types are acces
Hi Adrian,
Adrian Brock wrote:
On Mon, 2008-04-28 at 20:16 -0700, Stanley M. Ho wrote:
3.2 ModuleDefinition class
Two new methods are added in the ModuleDefinition class to return the
exported packages and member packages respectively. The export and
member definitions contained in the OSGi met
On Mon, 2008-04-28 at 20:16 -0700, Stanley M. Ho wrote:
> 3.2 ModuleDefinition class
> Two new methods are added in the ModuleDefinition class to return the
> exported packages and member packages respectively. The export and
> member definitions contained in the OSGi metadata are in package
> gran
