Hi! Is it possible to publish multiplatform libraries (with GRADLE_METADATA enabled) to JitPack? If I understand correctly, JitPack relies on the build task, which doesn’t produce the .module files... Is there a way to get around this? Thanks!

In the JitPack docs, https://jitpack.io/docs/BUILDING/, they say:

With maven-publishing plugin it will run

./gradlew build publishToMavenLocal

So I think it should include the

*.module

files, too. Does it not?

I played with the publishing settings and you’re right it seems the files are present. I’m now getting errors of the type: Required org.jetbrains.kotlin.platform.type ‘js’ and found incompatible value ‘jvm’. I’m still investigating but maybe you can point me in the right direction?

This particular statement says that the consumer wants a JS artifact and the producer's variant is a JVM one. So if it says so for each configuration, then it didn't find the JS target's variant (does your library have a JS variant? do you specify a dependency on the library 'root' module, not the JVM one?). Gradle usually prints a big and detailed error output listing all of the candidate variants explaining why each didn't match. Could you please share that?

./gradlew build --refresh-dependencies

Configure project :

Kotlin Multiplatform Projects are an experimental feature.

Task :compileKotlinJs FAILED

FAILURE: Build failed with an exception. * What went wrong: Execution failed for task ‘:compileKotlinJs’.

Could not resolve all files for configuration ‘:jsCompileClasspath’.

> Could not resolve com.github.egoossens.firestore-kotlin-mppbuild jvm3c94011c06. Required by: project : > com.github.egoossensfirestore kotlin mpp3c94011c06 > Unable to find a matching variant of com.github.egoossens.firestore-kotlin-mppbuild jvm3c94011c06: - Variant ‘jvm-api’: - Found artifactType ‘jar’ but wasn’t required. - Found org.gradle.status ‘release’ but wasn’t required. - Required org.gradle.usage ‘kotlin-api’ and found compatible value ‘java-api’. - Required org.jetbrains.kotlin.platform.type ‘js’ and found incompatible value ‘jvm’. - Variant ‘jvm-runtime’: - Found artifactType ‘jar’ but wasn’t required. - Found org.gradle.status ‘release’ but wasn’t required. - Required org.gradle.usage ‘kotlin-api’ and found compatible value ‘java-runtime-jars’. - Required org.jetbrains.kotlin.platform.type ‘js’ and found incompatible value ‘jvm’. - Variant ‘metadata-api’: - Found artifactType ‘jar’ but wasn’t required. - Found org.gradle.status ‘release’ but wasn’t required. - Required org.gradle.usage ‘kotlin-api’ and found compatible value ‘kotlin-api’. - Required org.jetbrains.kotlin.platform.type ‘js’ and found incompatible value ‘common’. > Could not resolve com.github.egoossens.firestore-kotlin-mppbuild metadata3c94011c06. Required by: project : > com.github.egoossensfirestore kotlin mpp3c94011c06 > Unable to find a matching variant of com.github.egoossens.firestore-kotlin-mppbuild metadata3c94011c06: Variant ‘metadata-api’: - Found artifactType ‘jar’ but wasn’t required. - Found org.gradle.status ‘release’ but wasn’t required. - Required org.gradle.usage ‘kotlin-api’ and found compatible value ‘kotlin-api’. - Required org.jetbrains.kotlin.platform.type ‘js’ and found incompatible value ‘common’. * Try: Run with --stacktrace option to get the stack trace. Run with --info or --debug option to get more log output. Run with --scan to get full insights. * Get more help at https://help.gradle.org

So do you explicitly declare a dependency on

com.github.egoossens.firestore-kotlin-mpp:build-jvm:3c94011c06

and

com.github.egoossens.firestore-kotlin-mpp:build-metadata:3c94011c06

? This is what the log looks like: it says Gradle tried to resolve a dependency on

com.github.egoossens.firestore-kotlin-mpp:build-jvm:...

for a JS consumer (

jsCompileClasspath

), which failed quite as expected. Did you try to replace them with a single dependency on

com.tastyelectrons.firestore-kotlin-mpp:build:...

?

hmm could there be a clash in my versioning? The .module file is referencing 0.1.0 but I’m using commit hashes on JitPack

Not sure if this kind of mismatch can influence anything at all; since Gradle found and listed the library's variants, it didn't object to the version in metadata not matching the Maven module version.

To answer your previous question, I’m only referencing the dependency in commonMain (not in the platform source sets). Note that I’m using the new MPP format with platform specific source sets instead of modules.

Then your dependency declaration should like like this:

commonMain {
    dependencies {
        implementation 'com.github.egoossens.firestore-kotlin-mpp:build:3c94011c06'
    }
}

Note that it references the module named

build

with no platform suffix (not

build-jvm

or

build-js

). The dependency kind,

api

or

implementation

, doesn't make difference, both should work.

yeah I think this was part of the problem. I tried that and I’m now getting Could not find com.tastyelectrons.firestore-kotlin-mppbuild js0.1.0. which I think comes from the version mismatch

Yeah maybe I'm starting to understand why:

Let me try that and see what happens

I'm not sure whether JitPack passes the version into the build somehow – if it does, you could also set the project's version from the commit ID and make those match.

cool, let me try that instead

Does it lead to the same error, Could not find com.tastyelectrons.firestore-kotlin-mppbuild js0.1.0?

Similar yeah except the version is correct now

I see. If publishing under the group ID chosen by JitPack is fine with you, then you may set the project's group in a similar way.

yeah I don’t mind... but I’m curious if there’s a way around that?

I believe Gradle relies on the module metadata of the variant written in the 'root' module's publication (https://jitpack.io/com/github/egoossens/firestore-kotlin-mpp/build/4bf33d302c/build-4bf33d302c.module), which points it to the incorrect Maven coordinates, see the

available-at

part:

{
      "name": "js-api",
      "attributes": {
        "artifactType": "jar",
        "org.gradle.usage": "kotlin-api",
        "org.jetbrains.kotlin.platform.type": "js"
      },
      "available-at": {
        "url": "../../build-js/4bf33d302c/build-js-4bf33d302c.module",
        "group": "com.tastyelectrons.firestore-kotlin-mpp",
        "module": "build-js",
        "version": "4bf33d302c"
      }
    },

Maybe they must always match. I personally didn't try to publish a module under mismatching Maven coordinates, so thanks for sharing your experience, that definitely needs to be taken into consideration.

Maybe that’s related? https://jitpack.io/docs/PRIVATE/#custom-domain

Yes it seems so.

Anyway I think the dependency problem is solved 🙂 Thanks a lot for your time, I really appreciate it!

You're welcome.