io7m opened a new issue, #52: URL: https://github.com/apache/felix-atomos/issues/52
The default Atomos boot layer seems to contain everything on the module path. This (obviously) includes all of the JDK and Java modules, but it also includes any other modules that a host application might be using. If I want to write a JPMS-modularized application that dynamically creates embedded OSGi containers running Atomos, it seems as though all of the modules my JPMS host application has are also made accessible to the OSGi container. There doesn't appear to be a way to turn this off, or to filter the list of modules that end up visible in the Atomos boot layer. For my use case, I'd be happy with an Atomos boot layer that _only_ contained the JVM's own modules. I would then create my own Atomos layer on top of that, containing only extra modules I wanted to expose to the OSGi container. Is there some way I can do this? -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: dev-unsubscr...@felix.apache.org.apache.org For queries about this service, please contact Infrastructure at: us...@infra.apache.org
