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

Posted to notifications@groovy.apache.org by "Paul King (Jira)" <ji...@apache.org> on 2026/10/20 01:27:02 UTC

[jira] [Closed] (GROOVY-11906) VMPlugin cleanup for Groovy 6

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

Paul King closed GROOVY-11906.
------------------------------

> VMPlugin cleanup for Groovy 6
> -----------------------------
>
>                 Key: GROOVY-11906
>                 URL: https://issues.apache.org/jira/browse/GROOVY-11906
>             Project: Groovy
>          Issue Type: Improvement
>            Reporter: Paul King
>            Assignee: Paul King
>            Priority: Major
>             Fix For: 6.0.0-alpha-1
>
>
> Since Groovy 6 has JDK17 minimum, the older JDK versions in the vmplugin hierarchy, while not causing any harm, are essentially offering no value by being split.
>  
> As a first step, I propose the following vmplugin refactoring:
> - Create v17/Java17.java extending Java16
> - Update VMPluginFactory to use only Java17
> - Deprecate Java8, Java9, Java10, Java16 for removal
> - Leave existing auxiliary files in place
> - Added @SuppressWarnings("removal") at call sites using the old classes
> Subsequently, we can choose to remove some of the older files and "push functionality up the hierarchy".



--
This message was sent by Atlassian Jira
(v8.20.10#820010)