[
https://issues.apache.org/jira/browse/MNG-8169?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17872574#comment-17872574
]
Rostislav Krasny commented on MNG-8169:
---------------------------------------
> Those who live on MinGW should set {{MAVEN_OPTS}} env variable, and they are
> directly passed to JVM.
This is not a good solution and could be used as a workaround only.
The right solution will be fixing this bug in the Jansi library itself and
using that fixed version in Maven instead of the current 2.4.1 one.
I sent both a bug report and a pull request with the fix into the Jansi project
more than a month ago but there was no reaction yet.
> MINGW support requires --add-opens java.base/java.lang=ALL-UNNAMED
> ------------------------------------------------------------------
>
> Key: MNG-8169
> URL: https://issues.apache.org/jira/browse/MNG-8169
> Project: Maven
> Issue Type: Bug
> Components: Core
> Affects Versions: 3.9.7, 3.9.8
> Reporter: Rostislav Krasny
> Priority: Major
>
> Running any Maven command on MINGW64 terminal of Git for Windows and probably
> in several other UNIX-mimicking environments prints out the "MINGW support
> requires --add-opens java.base/java.lang=ALL-UNNAMED" error message (can be
> printed several times during one Maven command) and can't get the right width
> of the terminal.
> This bug came from the Jansi dependency after it was upgraded from 2.4.0 to
> 2.4.1 version. For more information please see my bug report and my pull
> request in the Jansi project's GitHub:
> [https://github.com/fusesource/jansi/issues/290]
> [https://github.com/fusesource/jansi/pull/291]
> Since many developers use Maven on Windows together with Git for Windows and
> on its Git Bash environment based on MINGW this bug is important, in my
> opinion.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
