This is an automated email from the ASF dual-hosted git repository.
cstamas pushed a commit to branch master
in repository https://gitbox.apache.org/repos/asf/maven-gpg-plugin.git
The following commit(s) were added to refs/heads/master by this push:
new bbe6156 Add FAQ for "no pinentry" issue (#118)
bbe6156 is described below
commit bbe6156400212b3fe063d218399ba09c24795f44
Author: Tamas Cservenak <[email protected]>
AuthorDate: Tue Sep 10 18:48:07 2024 +0200
Add FAQ for "no pinentry" issue (#118)
---
src/site/fml/faq.fml | 11 +++++++++++
1 file changed, 11 insertions(+)
diff --git a/src/site/fml/faq.fml b/src/site/fml/faq.fml
index 279e66c..394960a 100644
--- a/src/site/fml/faq.fml
+++ b/src/site/fml/faq.fml
@@ -43,5 +43,16 @@ under the License.
</p>
</answer>
</faq>
+ <faq id="no-pinentry">
+ <question>Why am I getting "gpg: signing failed: No pinentry" while
releasing?</question>
+ <answer>
+ <p>
+ When plugin used in combination with <a
href="https://maven.apache.org/maven-release/maven-release-plugin/";>Maven
Release Plugin</a>
+ the GPG signing will happen in "batch mode". This implies that you
must either use GPG passphrase passed in
+ via environment variable (preferred on systems like CI systems are),
or, if on Workstation, using primed
+ gpg-agent is needed. Read more here about <a
href="usage.html#sign-artifacts-with-gnupg">GPG Agent priming</a>.
+ </p>
+ </answer>
+ </faq>
</part>
</faqs>
