Publish on Maven

[abhishiv]

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.

[aSemy]

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?

[abhishiv]

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!

[aSemy]

Because of significant deficiencies with the Gradle signing plugin

• SigningExtension and SignOperation should accept Provider<? extends Task> gradle/gradle#19903
• Make signing plugin support the configuration cache gradle/gradle#13470
• Signing plugin does not use configuration avoidance APIs and causes eager creation of tasks gradle/gradle#18477
• Can't add signatures to a Maven publication gradle/gradle#20934
• publish task from maven-publish plugin should work with configuration cache gradle/gradle#19842

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

• https://issues.sonatype.org/browse/OSSRH-67884
• https://issues.sonatype.org/browse/OSSRH-81412
• https://issues.sonatype.org/browse/OSSRH-81414
• https://issues.sonatype.org/browse/OSSRH-81419
• https://issues.sonatype.org/browse/OSSRH-81434
• https://issues.sonatype.org/browse/OSSRH-81435

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

[aSemy]

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.