Jeremy Wales wrote:
Thanks for your response, Richard.
So, working out what packages are available on the Class Path, and the
other
packages each uses, isn't hard (I've got something working and it seems
to
be fast enough) but then they need to be exported somehow. Readi
Thanks for your response, Richard.
> So, working out what packages are available on the Class Path, and the
> other
> > packages each uses, isn't hard (I've got something working and it seems
> to
> > be fast enough) but then they need to be exported somehow. Reading the
> OSGi
> > spec, it seems
Jeremy Wales wrote:
Hi,
I'm trying to come up with a way to expose all the packages which happen to
be available on the Class Path as proper OSGi package exports. Inspired by
Chapter 9 Migration in the JSR 277 Early Draft, which defines a
java.classpath module so modules can import from legacy J
Hi,
I'm trying to come up with a way to expose all the packages which happen to
be available on the Class Path as proper OSGi package exports. Inspired by
Chapter 9 Migration in the JSR 277 Early Draft, which defines a
java.classpath module so modules can import from legacy JARs, I thought
somethi
