Skip to content
This repository was archived by the owner on Sep 25, 2018. It is now read-only.
This repository was 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

@heuermh

Description

@heuermh

As an external developer, I shouldn't be code signing artifacts when running mvn package or mvn install locally, 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] ------------------------------------------------------------------------

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions