This is an automated email from the ASF dual-hosted git repository. sjaranowski pushed a commit to branch new-line-maven.config in repository https://gitbox.apache.org/repos/asf/maven-site.git
commit b9fe7c1257626cf039ab2ec73f0f7e3ac9080d4e Author: Slawomir Jaranowski <[email protected]> AuthorDate: Fri Feb 17 22:27:07 2023 +0100 Notice about new lines in maven.config --- content/markdown/configure.md | 12 ++++++++++-- 1 file changed, 10 insertions(+), 2 deletions(-) diff --git a/content/markdown/configure.md b/content/markdown/configure.md index 80c48f31..aaf782b9 100644 --- a/content/markdown/configure.md +++ b/content/markdown/configure.md @@ -75,8 +75,16 @@ options to a script but this can now simple being done by defining `${maven.proj configuration options for the `mvn` command line. For example things like `-T3 -U --fail-at-end`. So you only have to call Maven just by using `mvn -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 -`${maven.projectBasedir}/.mvn/maven.config` is located in the `${maven.projectBasedir}/.mvn/` directory; also works if in the root of a multi module build. +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 `${maven.projectBasedir}/.mvn/maven.config` is located in the `${maven.projectBasedir}/.mvn/` directory; also works if in the root of a multi module build. + +**NOTICE** starting with Maven **3.9.0** each single argument must be put in new line, so for the mentioned example your file will have content like: + +``` +-T3 +-U +--fail-at-end +``` ### `.mvn/jvm.config` file:
