This message was deleted.
# community-support
s
This message was deleted.
c
deps.txt
t
I'm not a Gradle expert when it comes to module files, but I know that Gradle prefers it's own published
*.module
files over any published
*.pom
file and in the former file(s) I see suspicious-looking back-references for variants like `jvmApiElements-published`: https://repo.maven.apache.org/maven2/io/github/charlietap/leftright/0.2.1/leftright-0.2.1.module
You could try and publish your library with module metadata generation disabled, like so:
Copy code
tasks.withType(GenerateModuleMetadata) {
    enabled = false
}
and see if this lets you consume your artifacts in your project.
Nice library btw, read your dev.to post!
❤️ 1
v
You could try and publish your library with module metadata generation disabled
Please don't, better fix the problem instead. If just for trying out, you can simply disable the usage of GMM on consumer side too.
c
At this point I can’t see a path forward without investing significantly more time learning the intricacies of the metadata/gradle/kmp plugin. I guess theres a simple mistake I’ve made but its non obvious
v
What problem do you actually see? If I do the
implementation("io.github.charlietap:leftright:0.2.2")
you suggested, I don't get any error.
Btw. your project is not too contributor friendly.
For example it requires to either change the version catalog or have a specific Amazon Java installed as it is also not auto-provisioned.
And even publishing to maven local requires signing configuration
Anyway, your main problem here is, that you are not reading your build output. 😉 You have several > Multiple publications with coordinates '...' are published to repository 'mavenLocal'. The publications 'jvm' in project '...' and 'kotlinMultiplatform' in project '...' will overwrite each other! which is the source of your problem most probably. In your build scripts you nail group/artifact/version of all publications to the same value, causing this warning and thus problem. You should at least remove the setting of artifact, then it probably works as expected. But actually I would also remove setting of group and version and better set it on the project instead. I think by just doing it on the publication, you for example cannot conveniently use the project in a composite build without manual substitutions. Also, disabling GMM as @Thomas Keller suggested would not change anything in this case.
c
@Vampire Thank you for the steer I will give this a go tonight
👌 1