This is an automated email from the ASF dual-hosted git repository.

slachiewicz pushed a commit to branch maven-clean-plugin-4.x
in repository https://gitbox.apache.org/repos/asf/maven-clean-plugin.git


The following commit(s) were added to refs/heads/maven-clean-plugin-4.x by this 
push:
     new 5cdd080  Give code blocks a real language instead of unknown
5cdd080 is described below

commit 5cdd0808464f6ad809863e9334ce9ed896b2322d
Author: Sylwester Lachiewicz <[email protected]>
AuthorDate: Mon Nov 2 14:10:42 2026 +0000

    Give code blocks a real language instead of unknown
---
 src/site/markdown/examples/delete_additional_files.md.vm | 6 +++---
 src/site/markdown/examples/ignoring-errors.md.vm         | 4 ++--
 src/site/markdown/examples/skipping-clean.md.vm          | 4 ++--
 src/site/markdown/usage.md.vm                            | 8 ++++----
 4 files changed, 11 insertions(+), 11 deletions(-)

diff --git a/src/site/markdown/examples/delete_additional_files.md.vm 
b/src/site/markdown/examples/delete_additional_files.md.vm
index 84a2bda..eca45ce 100644
--- a/src/site/markdown/examples/delete_additional_files.md.vm
+++ b/src/site/markdown/examples/delete_additional_files.md.vm
@@ -29,7 +29,7 @@ under the License.
 
 The Maven Clean Plugin will delete the `target` directory by default. You may 
configure it to delete additional directories and files. The following example 
shows how:
 
-```unknown
+```xml
 <build>
   [...]
   <plugin>
@@ -58,13 +58,13 @@ The Maven Clean Plugin will delete the `target` directory 
by default. You may co
 
 **Note:** The `directory` in the `fileset` is a relative path inside a 
project, in other words,
 
-```unknown
+```xml
   <directory>some/relative/path</directory>
 ```
 
 is equivalent to:
 
-```unknown
+```xml
   <directory>${esc.d}{basedir}/some/relative/path</directory>
 ```
 
diff --git a/src/site/markdown/examples/ignoring-errors.md.vm 
b/src/site/markdown/examples/ignoring-errors.md.vm
index 3c48dd4..0208187 100644
--- a/src/site/markdown/examples/ignoring-errors.md.vm
+++ b/src/site/markdown/examples/ignoring-errors.md.vm
@@ -28,7 +28,7 @@ under the License.
 
 To ignore errors when running the cleanup for a particular project, set the 
`failOnError` property to `false`.
 
-```unknown
+```xml
 <build>
   [...]
     <plugin>
@@ -44,6 +44,6 @@ To ignore errors when running the cleanup for a particular 
project, set the `fai
 
 You can also ignore them via command line by executing the following command:
 
-```unknown
+```shell
 mvn clean -Dmaven.clean.failOnError=false
 ```
diff --git a/src/site/markdown/examples/skipping-clean.md.vm 
b/src/site/markdown/examples/skipping-clean.md.vm
index 2b017d6..5c4c400 100644
--- a/src/site/markdown/examples/skipping-clean.md.vm
+++ b/src/site/markdown/examples/skipping-clean.md.vm
@@ -28,7 +28,7 @@ under the License.
 
 To skip running the cleanup for a particular project, set the `skip` property 
to `true`.
 
-```unknown
+```xml
 <build>
   [...]
     <plugin>
@@ -44,6 +44,6 @@ To skip running the cleanup for a particular project, set the 
`skip` property to
 
 You can also skip the cleaning via command line by executing the following 
command:
 
-```unknown
+```shell
 mvn clean -Dmaven.clean.skip=true
 ```
diff --git a/src/site/markdown/usage.md.vm b/src/site/markdown/usage.md.vm
index 0ce61d9..d895b21 100644
--- a/src/site/markdown/usage.md.vm
+++ b/src/site/markdown/usage.md.vm
@@ -33,7 +33,7 @@ Cleaning a Maven project using the command-line
 
 The Clean Plugin can be called to execute in the command-line without any 
additional configurations. Like the other plugins, to run the Clean Plugin, you 
use:
 
-```unknown
+```shell
   mvn clean:clean
 ```
 
@@ -41,13 +41,13 @@ where the first `clean` refers to the plugin's alias, and 
the second `clean` ref
 
 However, the Clean Plugin is a special plugin and is bound to its own special 
lifecycyle phase called `clean`. Thus, for simplicity, it can also be executed 
by using:
 
-```unknown
+```shell
   mvn clean
 ```
 
 or with other phases/goals like:
 
-```unknown
+```shell
   mvn clean package site
 ```
 
@@ -56,7 +56,7 @@ Running the Clean Plugin automatically during a build
 
 If for some reason, adding `clean` to the command-line is not option, the 
Clean Plugin can be put into a project's `pom.xml` so that it gets executed 
everytime the project is built. Below is a sample `pom.xml` for running the 
Clean Plugin in the `initialize` phase everytime the project is built:
 
-```unknown
+```xml
 <project>
   [...]
   <build>

Reply via email to