|
<plugin> |
|
<groupId>org.apache.maven.plugins</groupId> |
|
<artifactId>maven-gpg-plugin</artifactId> |
|
<version>1.6</version> |
|
<executions> |
|
<execution> |
|
<id>sign-artifacts</id> |
|
<phase>verify</phase> |
|
<goals> |
|
<goal>sign</goal> |
|
</goals> |
|
<configuration> |
|
<keyname>9F88D86AD9A0D91E</keyname> |
|
</configuration> |
|
</execution> |
|
</executions> |
|
</plugin> |
was introduced as part of
00180d1 as a prerequisite to the deployment to OSS Sonatype - see
https://central.sonatype.org/publish/requirements/#sign-files-with-gpgpgp.
While this works very elegantly in the context of artifact publication via GitHub Actions, this breaks local developer workflow while running mvn install. Supporting both workflows might require defining a profile to allow the artifact signing to be triggered conditionally.
jzarr/pom.xml
Lines 246 to 262 in d4f85aa
While this works very elegantly in the context of artifact publication via GitHub Actions, this breaks local developer workflow while running
mvn install. Supporting both workflows might require defining a profile to allow the artifact signing to be triggered conditionally.