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

Michael Osipov commented on MNG-8374:
-------------------------------------

No, Maven 4 requires Java 17 at build and runtime.

> 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
>
> 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)

Reply via email to