This repository has been archived by the owner on Sep 25, 2018. It is now read-only.
GPG artifact code signing should only be enabled in a release profile #71
Comments
|
Agreed - we'll look into this
|
heuermh
added a commit
to heuermh/phenopacket-reference-implementation
that referenced
this issue
Jul 12, 2016
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
As an external developer, I shouldn't be code signing artifacts when running
mvn packageormvn installlocally, rather the maven-gpg-plugin should only be enabled in a release profile.$ mvn install ... [INFO] Building jar: /Users/heuermh/working/phenopacket-reference-implementation/target/phenopackets-api-0.0.5-SNAPSHOT-javadoc.jar [INFO] [INFO] --- maven-gpg-plugin:1.5:sign (sign-artifacts) @ phenopackets-api --- /bin/sh: gpg: command not found [INFO] ------------------------------------------------------------------------ [INFO] BUILD FAILURE [INFO] ------------------------------------------------------------------------The text was updated successfully, but these errors were encountered: