Consider automating snapshot releases?

[lread]

Would it make sense to automatically deploy a SNAPSHOT release after each successful build on master?

I don't think this is happening after having a glance at the github workflow.

If I look at jfrog's repo, it doesn't seem to be happening regularly.

The README implies that deploying SNAPSHOT builds is a manual process.

I don't know how much work this is, so if it has been explored and rejected, I understand.

[robertpanzer]

Good idea.
We actually had that in the past for the 1.6.0 branch which was in development for a very long time before we made the first release:

asciidoctorj/.travis.yml

Line 28 in 0758c5f

after_success: if [ "${TRAVIS_BRANCH}" = "asciidoctorj-1.6.0" -a "${TRAVIS_PULL_REQUEST}" = "false" -a "${TRAVIS_JDK_VERSION}" = "oraclejdk8" ]; then ./gradlew clean build artifactoryPublish -x test ; fi

We "just" need to bring these steps to the Github Actions build.

[robertpanzer]

That said, in the future I'd like to get rid of the bintray plugin.
The whole current publishing configuration prevents us from going to the latest Java versions.