Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

vanilla mvn install should not use GPG #100

Open
DDvO opened this issue Apr 8, 2024 · 4 comments
Open

vanilla mvn install should not use GPG #100

DDvO opened this issue Apr 8, 2024 · 4 comments
Assignees
Labels
documentation Improvements or additions to documentation

Comments

@DDvO
Copy link
Member

DDvO commented Apr 8, 2024

On updating to the latest version 4.1.2, I got

[INFO] --- gpg:3.1.0:sign (sign-artifacts) @ CmpRaComponent ---
[INFO] Signing 6 files with default secret key.
gpg: directory '/Users/david/.gnupg' created
gpg: no default secret key: No secret key
gpg: signing failed: No secret key
[INFO] ------------------------------------------------------------------------
[INFO] BUILD FAILURE
[INFO] ------------------------------------------------------------------------

I see little point in signing the artifact(s) in a regular build or installation for normal users.

@DDvO
Copy link
Member Author

DDvO commented Apr 8, 2024

And retrying after generating a dummy key, I got:

[INFO] --- gpg:3.1.0:sign (sign-artifacts) @ CmpRaComponent ---
[INFO] Signing 6 files with default secret key.
gpg: signing failed: Inappropriate ioctl for device
gpg: signing failed: Inappropriate ioctl for device
[INFO] ------------------------------------------------------------------------
[INFO] BUILD FAILURE
[INFO] ------------------------------------------------------------------------
[INFO] Total time:  9.692 s
[INFO] Finished at: 2024-04-08T14:41:57+02:00
[INFO] ------------------------------------------------------------------------
[ERROR] Failed to execute goal org.apache.maven.plugins:maven-gpg-plugin:3.1.0:sign (sign-artifacts) on project CmpRaComponent: Exit code: 2 -> [Help 1]

@DDvO DDvO changed the title mvn build/install should not use GPG vanilla mvn build/install should not use GPG Apr 8, 2024
@DDvO DDvO changed the title vanilla mvn build/install should not use GPG vanilla mvn install should not use GPG Apr 8, 2024
@DDvO
Copy link
Member Author

DDvO commented Apr 8, 2024

Just found this workaround: -Dgpg.skip

@Akretsch Akretsch added the documentation Improvements or additions to documentation label Apr 9, 2024
@Akretsch
Copy link
Collaborator

Akretsch commented Apr 9, 2024

The different styles of building and deploying shall be documented and referred by the toplevel README.md?

@DDvO
Copy link
Member Author

DDvO commented Aug 30, 2024

Yes, please.
And maybe better not use GPG by default?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
documentation Improvements or additions to documentation
Projects
None yet
Development

No branches or pull requests

3 participants