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

Posted to issues@ignite.apache.org by "Nikita Amelchev (Jira)" <ji...@apache.org> on 2026/10/10 08:56:00 UTC

[jira] [Updated] (IGNITE-29133) Finalize the migration of Ignite Extensions to Java 17

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

Nikita Amelchev updated IGNITE-29133:
-------------------------------------
    Component/s: extensions

> Finalize the migration of Ignite Extensions to Java 17
> ------------------------------------------------------
>
>                 Key: IGNITE-29133
>                 URL: https://issues.apache.org/jira/browse/IGNITE-29133
>             Project: Ignite
>          Issue Type: Task
>          Components: extensions
>            Reporter: Nikita Amelchev
>            Assignee: Nikita Amelchev
>            Priority: Major
>
> Ignite has moved to Java 17, and the extensions are already built against the Java 17 {{{}ignite-parent{}}}. However, the migration was never finished: the build, launch scripts, example projects and docs still carry leftovers from Java 11. Some modules are still hidden behind a JDK profile, the test JVM options lag behind Ignite, and the scripts and examples still accept or target JDK 11. Finishing the migration makes the supported JDK versions explicit and keeps the extensions consistent with Ignite.



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