Publish on Maven

Question

Publish on Maven

abhishiv opened this issue 3 years ago · 4 comments

Hello, it would be great to have this package on maven.

In my case I'm stuck on Maven since am using cloud functions and they require maven pom.xml unless you want to build and upload a jar. All my dependencies including kotlinx.serialization are maven except this packages.

Answer 1 · 2022-05-30T16:32:37.000Z

I'll see what I can do. I did start the process of publishing it to Maven Central, but I got lost in all the varying options.

What happens if you add Jitpack as a repository? The pom.xml should be hosted there. What error are you getting?

Answer 2 · 2022-05-30T18:27:09.000Z

Hey @aSemy

Sorry my mistake - I had no idea about Jitpack. Just tried it and it works beautifully!

Thank you for a great module! In all JVM env this is the only module I could find which handles polymorphism and abstract classes sensibly!

Answer 3 · 2022-06-06T10:15:34.000Z

Because of significant deficiencies with the Gradle signing plugin

and Sonatype is very unfriendly in general, especially to non-JVM, non-Maven projects

So at the moment I'm not able to release to Maven Central.

There are some alternatives, but none are really suitable

While JitPack works, it's JVM only https://jitpack.io/#adamko-dev/kotlinx-serialization-typescript-generator
GitHub packages still requires a users generate and set an authentication token, which is a pain.

Gradle source dependencies are cool, but really really janky https://blog.gradle.org/introducing-source-dependencies

// ./settings.gradle.kts
sourceControl {
    gitRepository("https://github.com/adamko-dev/kotlinx-serialization-typescript-generator.git") {
        producesModule("dev.adamko.kxstsgen:kxs-ts-gen-core")
        producesModule("dev.adamko.kxstsgen:versions-platform")
    }
}

Sonatype Snapshots don't live very long

I might try setting up my own Maven repo... UPDATE nope, that project is not well organised - it's very un-Gradle

Answer 4 · 2022-07-16T16:14:37.000Z

It looks like Maven Central publishing is working now, even if it's janky (I get lots of errors about missing signatures and files, so I have to repetitively publish until the Sonatype Nexus stops complaining).

I would be nice to set up a GitHub action to automate publishing - but that's another ticket.