This is an automated email from the ASF dual-hosted git repository.
mbuenger pushed a commit to branch master
in repository https://gitbox.apache.org/repos/asf/maven-site.git
The following commit(s) were added to refs/heads/master by this push:
new 8814f2f0 Add documentation on maven.config comments (#837)
8814f2f0 is described below
commit 8814f2f09e792241a787581b9c3292d92943fce5
Author: Christopher Tubbs <ctubb...@apache.org>
AuthorDate: Sat Jul 26 03:36:22 2025 -0400
Add documentation on maven.config comments (#837)
Update the configure page to explain how to write comments in the
maven.config file.
---
content/markdown/configure.md | 5 ++++-
1 file changed, 4 insertions(+), 1 deletion(-)
diff --git a/content/markdown/configure.md b/content/markdown/configure.md
index 8fa4c2f3..a66ebc92 100644
--- a/content/markdown/configure.md
+++ b/content/markdown/configure.md
@@ -85,10 +85,13 @@ For example things like `-T3 -U --fail-at-end`. So you only
have to call Maven b
clean package` instead of `mvn -T3 -U --fail-at-end clean package` and not to
miss the `-T3 -U --fail-at-end` options on every call.
The `.mvn/maven.config` is located in the project's top level `.mvn` directory
and also works in the root of a multi module build.
-**NOTICE** Starting with Maven **3.9.0** each single argument must be put on a
new line, so for the mentioned example your file will have content like:
+**NOTICE** Starting with Maven **3.9.0**, each single argument must be put on
a new line, and lines beginning with `#`
+are treated as comments. Maven 3.8.x and older do not support comments in this
file. So, for the example mentioned
+above, your file could look like:
```
-T3
+# this is a comment
-U
--fail-at-end
```
