javakdb
javakdb copied to clipboard
Publishing to maven repo on releases
Depends on #10
Could potentially push to one of the main maven repos when going a github release (i.e. current travis build file has the ability to run scripts/etc only on release). Would need to incorporate version used in github release (i.e. v1.1 is pushed to maven as v1.1)
It would allow other Java projects to add javakdb as a dependancy & automatically pull down the jar/etc when they build instead of doing various manual steps.
Ref: General info https://maven.apache.org/repository/index.html Github actions to publish to central repo/etc https://docs.github.com/en/free-pro-team@latest/actions/guides/publishing-java-packages-with-maven Publishing to maven central https://dzone.com/articles/publish-your-artifacts-to-maven-central Sonatype info - https://central.sonatype.org/pages/ossrh-guide.html / https://central.sonatype.org/pages/requirements.html https://blog.travis-ci.com/2017-03-30-deploy-maven-travis-ci-packagecloud/
details in README.md