Skip to content

Latest commit

 

History

History
29 lines (21 loc) · 1.2 KB

NOTES.md

File metadata and controls

29 lines (21 loc) · 1.2 KB
Raw

Development notes

Local testing

I have a bash script for switching java versions. To make sure I'm on Java 8 for example,

jvm -u 8
source jvm --home

Then running

mvn clean test jacoco:report

will test and create a coverage report at target/site/jacoco/index.html

Release procedure

  1. Increment version identifier in pom.xml and commit.
  2. Tag the commit with the version number; e.g.: git tag v1.4.0
  3. When pushed, GitHub Action "Create Release" will create a draft Release.
  4. GitHub action "Publish to the Maven Central Repository" was intended to respond to that and execute the build and deploy. However that doesn't work because the GitHub Release is created as draft. Instead, just run it manually. (I imagine there's a way to automate this to be much smoother, but I'm an Actions noob so it will wait for now.)
  5. Log in to Maven Central Repository.
  6. Find the project in Staging Repositories.
  7. Close the repo, wait a few, then release it.
  8. (More manual steps in need of automation...) Download the artifacts (jar, source, and javadoc) and upload them to the GitHub Release created earlier. Add a changelog for the release. Publish it.