[
https://issues.apache.org/jira/browse/MNG-8374?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17899272#comment-17899272
]
Tamas Cservenak edited comment on MNG-8374 at 11/18/24 9:28 PM:
----------------------------------------------------------------
To be fair, the _complete_ line is like this:
"Java Development Kit (JDK) Maven 4.0+ requires JDK 17 or above to execute.
It still allows you to build against 8 and other JDK versions by using
toolchains."
was (Author: cstamas):
To be fair, the _complete_ like is like this:
"Java Development Kit (JDK) Maven 4.0+ requires JDK 17 or above to execute.
It still allows you to build against 8 and other JDK versions by using
toolchains."
> mvn uses option --enable-native-access
> --------------------------------------
>
> Key: MNG-8374
> URL: https://issues.apache.org/jira/browse/MNG-8374
> Project: Maven
> Issue Type: Bug
> Components: Command Line
> Affects Versions: 4.0.0-beta-5
> Reporter: Jochen Wiedmann
> Priority: Major
> Fix For: waiting-for-feedback, wontfix-candidate
>
>
> Sorry, if I am wrong, but it is my understanding that Maven 4 is still
> supposed
> to work with Java 8 as the build JVM. Fact is, it doesn't, if I use the
> JAVA_HOME
> variable to use Java 8 as the build JVM
>
> {{$ JAVA_HOME=/usr/lib/jvm/java-1.8.0 /home/jwi/opt/mvn/4.0.0-beta-5/bin/mvn
> -V
> Unrecognized option: --enable-native-access=ALL-UNNAMED
> Error: Could not create the Java Virtual Machine.
> Error: A fatal exception has occurred. Program will exit.
> }}
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
