Andres Almiray

If we keep shipping `layrry-launcher` as a shaded JAR then we either 1. Skip adding a full module definition (`module-info.java`) 2. Figure out a way to combine all of Layrry...

@sormuras then we'd have to rethink if `layrry-launcher--all.jar` (shaded artifact) should be published or not. If only there was a tool that would take a set of module descriptors and...

I guess for `layrry-launcher--all.jar` we'd strip `module-info.class` from the shaded jar, thus becoming just a regular fat jar that can be used with `classpath`, whereas the `layrry-launcher-.jar` is modular, does...

Ye gods, the Shrinkwrap JARs contain split packages and there are no `Auto-Module-Name` directives in their manifests. The module descriptor for `layrry-core` looks like this module org.moditect.layrry.core { exports org.moditect.layrry;...

Psst @sormuras -> https://github.com/aalmiray/layrry/commit/b2e382c31ae6af617ab0e974ae9a20e036777da9

Making the launcher a module can help with #50 Given that Shrinkwrap has not seen much work lately I think we can't expect the project to move into proper modules,...

This may be trickier than I thought. Enabling global transitivity may result in duplicate modules that need not be loaded again, for example ```yaml layers: log: modules: # - "org.apache.logging.log4j:log4j-api:2.14.0"...

Would it make sense to **deactivate** a later at runtime? Deactivation does not remove the layer as you'd like to keep the layer hierarchy in place. Deactivation "unloads and hides"...

As I understand Layrry's current layer model, if a Layer were to be removed (say the `plugins` layer is nuked), then it's parent-child relationship are lost. Layers relationships are immutable...

Alright, to begin with let's say that `Layer` supports a `tag` property that accepts `List`. One could express that in TOML as ```toml [layers.log] tags = ["logging", "log4j"] modules =...