You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository was archived by the owner on Aug 18, 2020. It is now read-only.
As mentioned in #96 (comment) and discussed on discord we want to publish the Api to Maven Central as of prealpha 3.
For preparation we should setup everything that is needed for that before the release:
We need to request access for the org.codeoverflow groupId at Sonatype (official guide).
We need to setup sbt to be able to publish to Maven Central. xerial/sbt-sonatype should do most of that for us.
I want to automate release related publishing tasks like this or the creation and uploading of deployments to releases for alpha 1 (I will create a issue for that at some point), but for prealpha 3 it is going to happen manually if all are okay with that.
The text was updated successfully, but these errors were encountered:
Internally we've decided to use Github Package Registry instead of Maven Central, but GPR currently does have its issues with sbt, hopefully these get resolved soon.
codeoverflow-org/chatoverflow-api@ae808ed has implemented everything that is needed.
Everyone with a github account that is in the codeoverflow org can now publish the api.
Initial setup: create a file at ~/.sbt/1.0/gpr-codeoverflow.sbt with the following content:
hlxid
changed the title
Prepare to publish Api to Maven Central on prealpha 3 release
Prepare to publish Api to GitHub Package Registry on prealpha 3 release
Nov 26, 2019
Description
As mentioned in #96 (comment) and discussed on discord we want to publish the Api to Maven Central as of prealpha 3.
For preparation we should setup everything that is needed for that before the release:
org.codeoverflow
groupId at Sonatype (official guide).xerial/sbt-sonatype should do most of that for us.
I want to automate release related publishing tasks like this or the creation and uploading of deployments to releases for alpha 1 (I will create a issue for that at some point), but for prealpha 3 it is going to happen manually if all are okay with that.
The text was updated successfully, but these errors were encountered: