In response to several comments about toolchains, I wonder if maven should
provide something a bit more user friendly for maven 4.
I'm thinking about:
* extracting the toolchain out of the plugin config (optional) in
something that could be parsed easily so that mvnd (or the maven script)
could use the correct JDK directly,
That would be limited to simple use cases (not those were compilation
and tests are run with different JDK)
* a command line tool similar to jenv tool which would be used to
- set up the initial toolchains (maybe automatically if possible) by
scanning the system for JDK in known locations
- list / add / remove / select toolchains
Le mar. 19 juil. 2022 à 18:25, Karl Heinz Marbaise <khmarba...@gmx.de> a
écrit :
> Hi to all,
>
> what do you think about using JDK17 as minimum requirement for running
> the future Apache Maven 4.0.0 ?
>
> Kind regards
> Karl Heinz Marbaise
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org
> For additional commands, e-mail: dev-h...@maven.apache.org
>
>
--
------------------------
Guillaume Nodet
