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/07 14:28:01 UTC

(maven-jdeprscan-plugin) branch master updated: Drop backslash escapes that Markdown does not need

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-jdeprscan-plugin.git


The following commit(s) were added to refs/heads/master by this push:
     new 2de0511  Drop backslash escapes that Markdown does not need
2de0511 is described below

commit 2de0511415fcf2bb9a92542c4553024ab7920ee7
Author: Sylwester Lachiewicz <sl...@apache.org>
AuthorDate: Fri Aug 7 11:57:22 2026 +0200

    Drop backslash escapes that Markdown does not need
    
    Pages converted from APT with an older doxia-converter carry an escape in front of
    punctuation that is not markup where it stands: a hyphen or underscore inside a word,
    a parenthesis, a full stop after a letter. The backslash renders as nothing and only
    makes the source harder to read and to edit.
    
    Only positions where the bare character can never be markup are touched. A full stop
    after a digit keeps its escape, so an ordered list marker cannot appear by accident,
    and angle brackets keep theirs, since <escapeString> would otherwise be read as a tag.
    Code spans, fenced blocks and link destinations are left alone.
---
 src/site/markdown/usage.md.vm | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/src/site/markdown/usage.md.vm b/src/site/markdown/usage.md.vm
index 16fe513..55ae7d2 100644
--- a/src/site/markdown/usage.md.vm
+++ b/src/site/markdown/usage.md.vm
@@ -57,6 +57,6 @@ The configuration element contains the configuration for the plugin [like any ot
 Requirements
 ------------
 
-Based on the foundation of the plugin it is required to have JDK 9 installed. This means either you have it configured via **JAVA\_HOME** which means to run the whole Maven build with JDK 9 or via **Toolchains**.
+Based on the foundation of the plugin it is required to have JDK 9 installed. This means either you have it configured via **JAVA_HOME** which means to run the whole Maven build with JDK 9 or via **Toolchains**.
 
 How to configure Maven related to Toolchains can be read in the [Toolchains documentation](https://maven.apache.org/guides/mini/guide-using-toolchains.html).