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

2021-07-04 Thread Michael Osipov (Jira)


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

Michael Osipov updated MNG-7121:

Fix Version/s: wontfix-candidate

> 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
> Fix For: wontfix-candidate
>
>
> 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)


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

2021-03-18 Thread Pablo Grisafi (Jira)


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

Pablo Grisafi updated MNG-7121:
---
Summary: better support for multiple JDK  (was: better support for multiple 
SDK)

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