Andres Almiray

In that case I'd guess it would be wise to `/s/modules/artifacts` in `Layer` to open the door for a `module` property, wouldn't you agree?

the more I think about having the launcher embedded in the jlinked image I get more questions. I can see (at least) the following scenarios: 1. All required modules are...

I think #12 is needed before we can tackle this, as the core classes must be packaged in a module, preferably a full module.

It's worth mentioning that marking the module as `open` did not make a difference.

As commented at https://github.com/moditect/layrry/issues/67#issuecomment-759715743 by @p-zalejko, the fix is to set an explicit classloader on the `FXMLLoder` instance. There's nothing to be done from Layrry's side other than documenting this...

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...

Running the demo application with the specified instructions leads to an exception before plugins can be loaded ```sh $ java -jar launcher-0.0.1-SNAPSHOT.jar May 02, 2021 5:04:19 PM org.jboss.shrinkwrap.resolver.impl.maven.logging.LogTransferListener transferFailed WARNING:...

Commenting out `"com.infradna.tool:bridge-method-annotation:1.13"` from the layers.yml configuration file results in the following error ```$ layrry --layers-config layers.yml SLF4J: Class path contains multiple SLF4J bindings. SLF4J: Found binding in [jar:file:///Users/aalmiray/.m2/repository/ch/qos/logback/logback-classic/1.2.3/logback-classic-1.2.3.jar!/org/slf4j/impl/StaticLoggerBinder.class] SLF4J:...

Digging further. Removing the plugin `tar.gz` file leads to the following error: ```java $ layrry --layers-config layers.yml SLF4J: Class path contains multiple SLF4J bindings. SLF4J: Found binding in [jar:file:///Users/aalmiray/.m2/repository/ch/qos/logback/logback-classic/1.2.3/logback-classic-1.2.3.jar!/org/slf4j/impl/StaticLoggerBinder.class] SLF4J:...

Alright, one more thing. Forcing Layrry to look into Maven Local by adding the following to `layers.yml`: ```yml resolve: remote: true workOffline: true ``` Yields the same error when the...