Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Migrate off of private bintray repository #35

Open
jrouly opened this issue Aug 21, 2021 · 8 comments · May be fixed by #44
Open

Migrate off of private bintray repository #35

jrouly opened this issue Aug 21, 2021 · 8 comments · May be fixed by #44

Comments

@jrouly
Copy link
Contributor

jrouly commented Aug 21, 2021

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?

Isammoc added a commit to gatling/sbt-openapi-generator that referenced this issue Oct 14, 2021
Motivation:
Official repository published to bintray that was sunset.

Modifications:
 * Remove bintray dependencies
 * Force version
 * Upgrade dependencies

Result:
Published in our own repository until official contributors take a decision.

Ref: OpenAPITools#35
@jrouly
Copy link
Contributor Author

jrouly commented Nov 24, 2021

@wing328 is this something you could help out with? I don't really have any context on where the other mainline OpenAPITools projects publish.

@nMoncho
Copy link

nMoncho commented Feb 17, 2022

@ckipp01
Copy link

ckipp01 commented Feb 17, 2022

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.

@monksy
Copy link

monksy commented Mar 4, 2022

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.

@russellremple
Copy link

same

@ckipp01
Copy link

ckipp01 commented Aug 31, 2022

@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.

@ckipp01 ckipp01 linked a pull request Aug 31, 2022 that will close this issue
@jrouly
Copy link
Contributor Author

jrouly commented Oct 20, 2022

Apologies for my absence, thanks for taking this on @ckipp01 it's much appreciated.

@wing328
Copy link
Member

wing328 commented Mar 26, 2024

v7.3.0 sbt openapi generator published.

please give it a try when you've time

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging a pull request may close this issue.

6 participants