Andres Almiray

Tried different distros of `11.0.10`. All of them break with the same error ```sh Java version: 11.0.10, vendor: Azul Systems, Inc., runtime: /Users/aalmiray/.sdkman/candidates/java/11.0.10-zulu/zulu-11.jdk/Contents/Home Java version: 11.0.10, vendor: Amazon.com Inc., runtime:...

Adding @AlmasB For this to work the Layrry API would have to support defining module ids as inputs in its configuration. Right now only Maven coordinates are allowed, for example...

Probably related to #50

Right, we'd have to test that theory, won't we? 😏 If all jlinked modules can't be put into separate ModuleLayers then the only benefit I can see for the time...

Alright, so I did some investigation and I found the following: - built a custom jlink image with the following module descriptor (app is just a simple JavaFX app to...

Well, that's a lot of ... Kotlin code. If I understood that example correctly, the nexus plugin is only applied to the root while the subprojects configure themselves with java-library,...

Good grief, what if I have more than 50+ projects (as Ikonli does). Do you expect people to: a) manually invoke :X:publishToSonatype where x = the number of projects? b)...

> > How then must a subproject be marked to be skipped from uploading to a staging repository? > > Well, Gradle does whatever you ask it to do. If...

That would be case b). Not all projects are publishable (for whatever reason) hence why I used the word subset in the beginning.

Add up that some subprojects are publishable, just not to Maven Central. Could be to other Maven compatible repositories (non Nexus managed), could be a Gradle plugin (which would meet...