You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@maven.apache.org by sl...@apache.org on 2026/08/10 00:44:09 UTC
(maven-gpg-plugin) 01/01: Keep the FAQ quotation marks straight
This is an automated email from the ASF dual-hosted git repository.
slachiewicz pushed a commit to branch faq-keep-straight-quotes
in repository https://gitbox.apache.org/repos/asf/maven-gpg-plugin.git
commit 2dc56719955816b16d7e7065bc044e35b6925e2f
Author: Sylwester Lachiewicz <sl...@apache.org>
AuthorDate: Mon Aug 10 02:43:59 2026 +0200
Keep the FAQ quotation marks straight
The FML page rendered straight quotation marks, being XML. In Markdown
flexmark's smart-punctuation rewrites a bare " into a typographic pair,
so the converted page changed what the reader sees:
"gpg: signing failed: No pinentry" -> “gpg: signing failed: No pinentry”
That matters here because both quoted strings are things a reader copies:
one is the literal error message people search for, the other a mode
name. Writing " in the source keeps them straight, which is the
convention the already-converted pages in maven-site-plugin use.
Verified by rebuilding the site and comparing against the FML rendering:
the quotation marks match the original again, and no anchor changed.
Generated-by: Claude Opus 5 (1M context)
---
src/site/markdown/faq.md | 6 +++---
1 file changed, 3 insertions(+), 3 deletions(-)
diff --git a/src/site/markdown/faq.md b/src/site/markdown/faq.md
index 25dd33f..e22913f 100644
--- a/src/site/markdown/faq.md
+++ b/src/site/markdown/faq.md
@@ -27,7 +27,7 @@ under the License.
1. [What is GnuPG?](#question1)
2. [Why is the site descriptor not signed?](#site-descriptor)
-3. [Why am I getting "gpg: signing failed: No pinentry" while releasing?](#no-pinentry)
+3. [Why am I getting "gpg: signing failed: No pinentry" while releasing?](#no-pinentry)
<a id="question1"></a>
@@ -46,10 +46,10 @@ Maven Site Plugin 2.1.1+ which contains the required fix (see also
<a id="no-pinentry"></a>
-### Why am I getting "gpg: signing failed: No pinentry" while releasing?
+### Why am I getting "gpg: signing failed: No pinentry" while releasing?
When plugin used in combination with
[Maven Release Plugin](https://maven.apache.org/maven-release/maven-release-plugin/) the GPG signing will
-happen in "batch mode". This implies that you must either use GPG passphrase passed in via environment
+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 [GPG Agent priming](passphrase.html#Retrieve_passphrase_via_gpg-agent).