[jira] [Commented] (MNG-7684) With Maven 3.9.0, `maven.config` requires each flag on a separate line

["Daniel Martin (Jira)" <ji...@apache.org>]

    [ https://issues.apache.org/jira/browse/MNG-7684?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17707243#comment-17707243 ] 

Daniel Martin commented on MNG-7684:
------------------------------------

This is so dumb... The breaking change was completely unnecessary and the new version is just worse. Why couldn't you just keep the old behavior? You waste people's time and energy for no reason whatsoever...

> 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 git@github.com: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)