This is an automated email from the ASF dual-hosted git repository.
slachiewicz 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 7a1fbe5 Give code blocks a real language instead of unknown
7a1fbe5 is described below
commit 7a1fbe5d3933d0d44de6b5bde75fb222f8de83c3
Author: Sylwester Lachiewicz <[email protected]>
AuthorDate: Sun Nov 1 15:17:02 2026 +0000
Give code blocks a real language instead of unknown
---
src/site/markdown/passphrase.md | 6 +++---
src/site/markdown/usage.md.vm | 2 +-
2 files changed, 4 insertions(+), 4 deletions(-)
diff --git a/src/site/markdown/passphrase.md b/src/site/markdown/passphrase.md
index 7cff1c7..ba4e594 100644
--- a/src/site/markdown/passphrase.md
+++ b/src/site/markdown/passphrase.md
@@ -65,7 +65,7 @@ read -s -p "Enter your GnuPG key passphrase: "
MAVEN_GPG_PASSPHRASE; mvn release
Instead of specifying the passphrase on the command line, you can place it in
your local `settings.xml` either in clear or
[encrypted](/guides/mini/guide-encryption.html) text.
-```unknown
+```xml
<settings>
[...]
<servers>
@@ -82,7 +82,7 @@ Instead of specifying the passphrase on the command line, you
can place it in yo
To allow discovery of keyname and passphrase at build time, configure this
plugin to map both _keyname_ and _passphraseServerId_ to a fixed property.
-```unknown
+```xml
<project>
...
<build>
@@ -113,7 +113,7 @@ To allow discovery of keyname and passphrase at build time,
configure this plugi
and use local `settings.xml` to discover the passphrase via the keyname
-```unknown
+```xml
<settings>
[...]
<servers>
diff --git a/src/site/markdown/usage.md.vm b/src/site/markdown/usage.md.vm
index 4de3b29..47fc419 100644
--- a/src/site/markdown/usage.md.vm
+++ b/src/site/markdown/usage.md.vm
@@ -38,7 +38,7 @@ This is agnostic of the signing mechanism
Add the plugin to your `pom.xml` like this:
-```unknown
+```xml
<project>
...
<build>