Open arashi01 opened 1 year ago
@hamnis Let me know your thoughts.
Thanks for this.
We are limited to the jdk version which maven uses. If maven > jdk8 then we must use that. Its probably doubtful that maven will swich jdk target within a major release.
I am also somewhat skeptical to use old jdk versions for building. If you need to make sure we use only jdk-libraries that are on jdk-8, we can use the -release 8
compiler flag with a new jdk.
With regards to jdk8, I have fixed that in master. If you want to rebase this branch on top of master, that would be great.
Quick take at solving issues like #71 by switching publishing to CI.
With this setup, every tag starting with
v
will be deployed to Sonatype automatically.For it to work, a number of Github Secrets will need to be added as specified below.
For the GPG key, I would personally create another key specifically used for CI publishing, to avoid exposing your existing key to any possible vulnerabilities.
PUBLISH_USER
PUBLISH_USER_PASSPHRASE
GPG_SIGNING_KEY_ID
gpg --list-keys --keyid-format=long
)GPG_SIGNING_KEY
gpg --export-secret-keys --armour %GPG_KEY_ID%
)GPG_SIGNING_KEY_PASSPHRASE