You are viewing a plain text version of this content. The canonical link for it is here.

Posted to issues@maven.apache.org by "Michael Osipov (Jira)" <ji...@apache.org> on 2022/02/27 18:47:00 UTC

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

     [ https://issues.apache.org/jira/browse/MNG-7121?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Michael Osipov closed MNG-7121.
-------------------------------
    Fix Version/s:     (was: wontfix-candidate)
       Resolution: Won't Fix

Deliberately saying that this won't fix this.

> 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.20.1#820001)