That one needs java to *RUN* maven is an implementation detail for me
and the actual java version do not matter.
At best maven would ship with whatever JVM is required, or has a
launcher that downloads one or ... e.g. for Eclipse IDE (and other
software as well) one simply downloads a package (maybe with installer)
that is specific for a platform, so the same could work for maven, so
simply ship a "maven-runtime-jvm" with it...
Then there is java used for *COMPILE* and with the -release flags today
this does not matter much either and the maven-compiler-plugin should
offer whatever suffice to find/use the best to compile.
Then there might be java used to *RUN/TEST* an application where one
might want to test several ones or a specific one, but this is then best
configured separately from RUN maven or COMPILE code jdks...
Of course it is *CONVENIENT* to use the same java for each of the cases,
but its not a requirement, and maybe one should just make it more
convenient to use different JVMs for the different cases ... So if I
configure my test to run on java 8, maven should simply either find or
download a suitable JVM (maybe from maven central), if I have very
special requirements on the actual JVM vendor or version one can still
configure it explicitly, but I would assume that for > 99% it is simply
irrelevant if its Adpotium, OpenJDK, Oracle, Azul, ... whatever, all
that counts is it is a Java 1.8 so I can say I have tested it with (one)
Java 1.8 compliant JVM! And i should not need any setup (beside
downloading maven).
To some extend, maven can even ship with a JDK8, 11, 17 and 21 out of
the box!
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org
For additional commands, e-mail: dev-h...@maven.apache.org
