Closed jrouly closed 1 month ago
@wing328 is this something you could help out with? I don't really have any context on where the other mainline OpenAPITools projects publish.
@jrouly @wing328 Would it possible to publish the plugin at https://scala.jfrog.io/ui/native/sbt-plugin-releases/org.openapitools/sbt-openapi-generator, this is were we get redirected from https://repo.scala-sbt.org/scalasbt/sbt-plugin-releases
For some more context, JFROG is read only for sbt plugins now. To release the official recommendation is to instead just publish to Sonatype OSSR. If you're not familiar with how that is done on the sbt side, the link above should give you general instructions on how to set up an account and claim the space. Related I'd recommend looking into sbt-ci-release to just automate this whole thing for you. It'll by far be the easiest solution. If you need help setting this up need a pr to get you started, don't hesitate to say so. I'm happy to help.
Looks like much of the other sbt-openapi generator projects are being published on the central repo. Why isn't this?
I can't seem to use the plugin because it doesn't know where to grab it.
same
@jrouly would you be open to a PR addressing this? I see there are other artifacts being pushed to Maven centeral here: https://repo1.maven.org/maven2/org/openapitools/. I'm happy to send in a pr adding in https://github.com/sbt/sbt-ci-release, which is what a lot of open source sbt plugins are using. All you'd need to do is ensure the env variables are added to this repository. That's assuming you have access to the key to sign and the sonatype creds. If I sent in a PR adding this would you be able to update the secrets and push a release?
This is sort of a last effort before we fork and publish this internally, which we'd love to avoid.
Apologies for my absence, thanks for taking this on @ckipp01 it's much appreciated.
v7.3.0 sbt openapi generator published.
please give it a try when you've time
Bintray was sunset a while ago. Artifacts can no longer be published against it.
What is the plan for the OpenAPITools repository more broadly for artifact management?