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-compiler-plugin.git
The following commit(s) were added to refs/heads/master by this push:
new 40a8237c Give code blocks a real language instead of unknown
40a8237c is described below
commit 40a8237c66eb403388faf7e1a6e651f28912ac54
Author: Sylwester Lachiewicz <[email protected]>
AuthorDate: Sun Nov 1 15:17:30 2026 +0000
Give code blocks a real language instead of unknown
---
src/site/markdown/examples/compile-with-memory-enhancements.md.vm | 2 +-
src/site/markdown/examples/jpms_args.md.vm | 2 +-
src/site/markdown/examples/module-info.md.vm | 4 ++--
src/site/markdown/examples/pass-compiler-arguments.md.vm | 2 +-
src/site/markdown/non-javac-compilers.md.vm | 2 +-
src/site/markdown/usage.md.vm | 6 +++---
6 files changed, 9 insertions(+), 9 deletions(-)
diff --git a/src/site/markdown/examples/compile-with-memory-enhancements.md.vm
b/src/site/markdown/examples/compile-with-memory-enhancements.md.vm
index 9fcfdb3e..d635be03 100644
--- a/src/site/markdown/examples/compile-with-memory-enhancements.md.vm
+++ b/src/site/markdown/examples/compile-with-memory-enhancements.md.vm
@@ -28,7 +28,7 @@ under the License.
The Compiler Plugin accepts configurations for `meminitial` and `maxmem`. You
can follow the example below to set the initial memory size to 128MB and the
maximum memory usage to 512MB:
-```unknown
+```xml
<project>
[...]
<build>
diff --git a/src/site/markdown/examples/jpms_args.md.vm
b/src/site/markdown/examples/jpms_args.md.vm
index fde081fb..fa34bf86 100644
--- a/src/site/markdown/examples/jpms_args.md.vm
+++ b/src/site/markdown/examples/jpms_args.md.vm
@@ -39,7 +39,7 @@ If any of these arguments is used, the `META-INF/jpms.args`
is created. Every ar
The `--patch-module` values are different compared to the original values
passed to the compiler. According to the specification it looks like
`--patch-module <module>=<file>(<pathsep><file>)*` However, files are system
specific. For that reason the module names are used. If the jar itself contains
the patchcode, then an `_` (underscore) is used. As separators a `, ` (comma +
space) is used.
-```unknown
+```text
--patch-module
<module>=<module>(, <module>)*
```
diff --git a/src/site/markdown/examples/module-info.md.vm
b/src/site/markdown/examples/module-info.md.vm
index 6a86947c..75b45452 100644
--- a/src/site/markdown/examples/module-info.md.vm
+++ b/src/site/markdown/examples/module-info.md.vm
@@ -45,7 +45,7 @@ In case you want the project to be Java 6, 7 or 8 compatible,
you can simply use
The easiest way is to use Java 9 as the runtime for Maven, by setting
`JAVA_HOME=/path/to/jdk-9` before running `mvn`. But if you want to use an
older Java runtime for Maven, you can use the maven-toolchain-plugin to specify
the shared JDK or a custom jdkToolchain and refer to the JDK 9 installation on
your system.
-```unknown
+```xml
<project>
[...]
<build>
@@ -99,7 +99,7 @@ Given that Maven 3 requires newer Java release at runtime,
you'll absolutely nee
You could add a jdkToolchain to do base-compile execution-block as well
referring to JDK 5.
-```unknown
+```xml
<project>
[...]
<build>
diff --git a/src/site/markdown/examples/pass-compiler-arguments.md.vm
b/src/site/markdown/examples/pass-compiler-arguments.md.vm
index e510cdd0..7df4848a 100644
--- a/src/site/markdown/examples/pass-compiler-arguments.md.vm
+++ b/src/site/markdown/examples/pass-compiler-arguments.md.vm
@@ -28,7 +28,7 @@ under the License.
Sometimes, you need to pass compiler arguments that are not handled by the
Compiler Plugin itself but are supported by the `compilerId` selected. For such
arguments, use the Compiler Plugin's `compilerArgs` parameter The following
example passes compiler arguments to the `javac` compiler:
-```unknown
+```xml
<project>
[...]
<build>
diff --git a/src/site/markdown/non-javac-compilers.md.vm
b/src/site/markdown/non-javac-compilers.md.vm
index 793c9aad..e01c543b 100644
--- a/src/site/markdown/non-javac-compilers.md.vm
+++ b/src/site/markdown/non-javac-compilers.md.vm
@@ -44,7 +44,7 @@ Using The Other Plexus Compilers
To use any of the non-javac compilers, you need to make the artifact available
in the classpath when the Compiler Plugin runs. This is possible by adding the
dependency when declaring the plugin in your project's `pom.xml`. The example
below shows how to use the `csharp` compiler:
-```unknown
+```xml
<project>
[...]
<build>
diff --git a/src/site/markdown/usage.md.vm b/src/site/markdown/usage.md.vm
index 8511e91d..a7e1c08e 100644
--- a/src/site/markdown/usage.md.vm
+++ b/src/site/markdown/usage.md.vm
@@ -31,13 +31,13 @@ Compiling Your Java Sources
The goals for the Compiler Plugin are bound to their respective phases in the
build lifecycle. So to compile your sources, you need only to tell maven until
which lifecycle to execute. The following will compile your sources:
-```unknown
+```bash
mvn compile
```
To compile your test sources, you'll do:
-```unknown
+```bash
mvn test-compile
```
@@ -48,7 +48,7 @@ Configuring Your Compiler Plugin
Since the Compiler Plugin executes automatically during their phases, you
don't have to put `executions` unlike many other plugins. However, you should
specify the version of the Compiler Plugin.
-```unknown
+```xml
<project>
...
<build>