tjwatson commented on issue #51: URL: https://github.com/apache/felix-atomos/issues/51#issuecomment-1118641494
The issue is that Java Module System will only pull in the modules on the module path that are required from the starting module (you specified `-m org.apache.felix.atomos`). That does not pull in all your "modules" from the `plugins/`folder. To add all your modules you need to specify the java option `--add-modules=ALL-MODULE-PATH` which will force all of the modules on the module path to be included in a JPMS runtime resolution. But when I do that I get this: ``` java --add-modules=ALL-MODULE-PATH -p plugins/ -m org.apache.felix.atomos java.lang.module.FindException: Module org.osgi.service.cm not found, required by org.fipro.ds.command ``` Note that we are in the process of removing org.osgi.service.cm from the org.eclipse.osgi.services and having it instead require-reexport this org.osgi.service.cm bundle. That may help you in this case. But for now I would avoid trying to use `org.eclipse.osgi.services` in such scenarios and instead pull in the OSGi WG bundles that provide the APIs as much as possible for the module path scenarios. -- 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: [email protected] For queries about this service, please contact Infrastructure at: [email protected]
