Publish Gradle Module Metadata with platform-specific runtime variants

[jjohannes]

Hi from Gradle 👋

I was just checking how LWJGL3 is published and was delighted to see that you are already using the maven-publish plugin. I wanted to let you know that with Gradle 6 we are supporting a new metadata format called Gradle Module Metadata that would allow you to publish metadata that knows about jars containing native code and would allows Gradle to automatically pick the correct native jar. I actually used LWJGL as an example in our documentation to illustrate that use case:

https://docs.gradle.org/6.0-rc-3/userguide/component_metadata_rules.html#adding_variants_for_native_jars

I don't know how interesting this is for you, but if you get your build configured to publish Gradle Module Metadata correctly, it would make it really easy to use lwjgl3 as a dependency in a Gradle build like this (that's a sample repository I created to demonstrated some use cases).

I am happy to help here, if you are interested.

[elect86]

I've been playing with Gradle Metadata and attributes, thanks to Jendrik help and past efforts in this direction

I'd like to pick up this issue back and provide a PR, if this is fine for you, @Spasi

[Spasi]

@elect86 Sure, go ahead.