why don't we use sbt-sonatype?

[SethTisue]

what's the advantage of going through bintray-sbt, given that ultimately the artifacts are destined for Sonatype instead?

as @xerial points out, using sbt-sonatype could save us the trouble of having to use the Sonatype web UI to close and release the staging repos. that costs an extra 5 minutes or so (longer if it's been a while and we need to remember exactly how it goes).

currently we use the manual step:

• as an opportunity for last-second sanity-checking
• as a way for the Scala team to retain control over the final step, instead of ceding it entirely to community maintainers? I'm not actually sure if this was an intentional aspect of this process, or it just sort of turned out that way?

[jvican]

You may want to use sbt-release-early, which protects you against common pitfalls, has great docs, and improves upon sbt-sonatype in several ways, allowing you to customize the release pipeline and double checking release invariants before an actual push to Sonatype. https://github.com/scalacenter/sbt-release-early/wiki

[SethTisue]

resolved by @lrytz in #65 (by using sbt-ci-release, which includes sbt-sonatype)

[lrytz]

Actually I think this ticket suggests to release the plugin to sonatype/maven instead of bintray, not the projects using the plugin 🙂 but I got confused as well.

[SethTisue]

ha, I see now that the ticket description I wrote is confused between those two interpretations

for the record,

• the "projects using the plugin" interpretation is what is now fixed
• as for the "release the plugin" interpretation, I think sbt plugins are normally published to bintray and there's no reason I know of to change that

[lrytz]

👍 that's fine with me. publishing to bintray is really simple once it's set up, i find.

https://github.com/olafurpg/sbt-ci-release#how-do-i-publish-sbt-plugins suggests publishing sbt plugins to maven central is also common these days.

[SethTisue]

since Bintray is going away, I ended up doing this in #121 — we are now publishing the plugin itself using sbt-ci-release (which incorporates sbt-sonatype)