aalmiray
commented
3 years ago Could you share the layer configuration file? Please obfuscate or change the names of any non-public dependencies/modules you may have in your application to retain privacy (if warranted).
If the code is available from a public repository even better.
If I understood correctly, the layers configuration could look like this
[layers.core]
modules = [
"com.acme:some-other-dependency:{{project_version}}",
"com.acme:spring.data.commons:{{project_version}}",
"org.moditect.layrry:layrry-platform:{{layrry_version}}"]
[layers.plugins]
parents = ["core"]
directory = "plugins"
[main]
module = "com.acme.launcher"
class = "com.acme.launcher.Main"If this is the case then any plugins that are added/removed from the plugins layer will have access to classes defined in the core layer, regardless of how these plugin modules are configured for compilation.
mortharia
Hey,
We use Layrry to test a plugins based application. From the module layers process, we understand that when the core layer use a module, suppose spring.data.commons, the plugins should not include it in their layers. So for our application, we tag this shared module (spring.data.commons) as required in the module-info of the plugins but we include its maven dependency as provided to make sure they compile, .
The problem is when we run the application and request a plugin service, we get a ClassNotFoundException for classes invoked by the plugin from the shared module packages!!!
Have you had this problem and any idea to solve it?
Thank you.