[
https://issues.apache.org/jira/browse/MNG-7684?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17684919#comment-17684919
]
ASF GitHub Bot commented on MNG-7684:
-------------------------------------
Stephan202 commented on code in PR #380:
URL: https://github.com/apache/maven-site/pull/380#discussion_r1097861554
##########
content/markdown/docs/3.9.0/release-notes.md:
##########
@@ -43,6 +43,7 @@ If you have any questions, please consult:
* Several backports from Maven 4.x line.
* Long outstanding issue fixes from Maven 3.8.x line.
* General fixes and improvements.
+* Each line in `.mvn/maven.config` is now interpreted as a single argument.
That is, if the file contains multiple arguments, these must now be placed on
separate lines.
Review Comment:
I'm certainly open to other ways of phrasing this; just lemme know :)
> With Maven 3.9.0, `maven.config` requires each flag on a separate line
> ----------------------------------------------------------------------
>
> Key: MNG-7684
> URL: https://issues.apache.org/jira/browse/MNG-7684
> Project: Maven
> Issue Type: Bug
> Affects Versions: 3.9.0
> Environment: Maven 3.9.0
> Ubuntu 20.04.5 LTS
> Bash shell
> Reporter: Stephan Schroevers
> Priority: Major
>
> Prior to Maven 3.9.0, the {{.mvn/maven.config}} file supported multiple flags
> on the same line. As of Maven 3.9.0 the flags must be on separate lines. I
> _assume_ that this is an unintentional regression.
> To reproduce, run:
> {code:sh}
> git clone [email protected]:PicnicSupermarket/error-prone-support.git
> cd error-prone-support
> git checkout d1f513373fffe21fa463a9d6978cdfa8940e1ce4
> mvn -version
> {code}
> With Maven 3.8.7 the {{mvn -version}} command completes successfully. With
> Maven 3.9.0 it fails with:
> {noformat}
> Unable to parse maven.config file options: Unrecognized option: --batch-mode
> --errors --strict-checksums
> {noformat}
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
