Use gpg1 for client-side actions.

JGit has limited support for GPGv2 KBX files. Switching to gpg1 and legacy keyring files enables proper signing of commits.
This commit is contained in:
Greg L. Turnquist
2023-01-23 11:16:34 -06:00
parent ae2bc720f4
commit 949b92bb8a
7 changed files with 12 additions and 60 deletions

View File

@@ -5,7 +5,7 @@ git.password=${GITHUB_TOKEN}
#git.gpg.keyname=B3B6F3E392A8615C65A98FC51F33293B709FA3E2
#git.gpg.passphrase=${GIT_SIGNING_KEY_PASSWORD}
#git.gpg.executable=/usr/bin/gpg
#git.gpg.executable=/usr/bin/gpg1
deployment.username=${REPO_SPRING_IO_USR}
deployment.password=${REPO_SPRING_IO_PSW}
@@ -16,7 +16,7 @@ deployment.maven-central.stagingProfileId=${STAGING_PROFILE_ID}
deployment.maven-central.gpg.keyname=E2ACB037933CDEAAB7BF77D49A2C7A98E457C53D
deployment.maven-central.gpg.passphrase=${MAVEN_SIGNING_KEY_PASSWORD}
deployment.maven-central.gpg.executable=/usr/bin/gpg
deployment.maven-central.gpg.executable=/usr/bin/gpg1
sagan.key=n/a