[jira] [Commented] (MNG-7121) better support for multiple JDK

["Michael Osipov (Jira)" <ji...@apache.org>]

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

Michael Osipov commented on MNG-7121:
-------------------------------------

I understand your request, but truly believe that this is too much burden on us to have this kind of logic in Maven Core. From my experience such huge improvement requests disappear in JIRA oblivion after some years because no one has the time and motivation to work on it. Moreover, negotiating consistent coordinates across JDK vendors is a huge task.
I would propose to setup a webserver to host the JDKs you need and use booter shell scripts to solve that problem.
If someone wants to propose a technical draft, please do so. I will leave this open.

> better support for multiple JDK
> -------------------------------
>
>                 Key: MNG-7121
>                 URL: https://issues.apache.org/jira/browse/MNG-7121
>             Project: Maven
>          Issue Type: New Feature
>          Components: core
>            Reporter: Pablo Grisafi
>            Priority: Major
>
> Java evolves at a much faster pace now. In the compay I work for we have projects on Java 6 (sadly yes), 8, 11 and 15.
>  
> The toolchains plugin helps, but it involves manually editing an  xml file, and in my experience people tend to forget about it.
>  
> I think a better user experiense would be a ~/.m2/jdks folder, with one subfolder per jdk, a little like sdkman does it.
> Maven could even automaticlly download the one you need for a specific project if it is not already present, like it does with any dependency. It will be more portable and less manual work. Dependency handling and jdk handling will be managed be maven in a consistent way, cloning a project from github will be way more straightforward.



--
This message was sent by Atlassian Jira
(v8.3.4#803005)