[
https://issues.apache.org/jira/browse/NIFI-9280?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
David Handermann updated NIFI-9280:
-----------------------------------
Description:
17, the next LTS version of Java, has been released. NiFi should support
running on it. A week or two ago, I tried and NiFi wouldn't start when 17 was
used.
This may need to wait for NiFi version 2 when Java 11 will be minimum supported
Java version. But, an attempt to support 8,11,and 17 can be made. Perhaps build
with 17 but target 8.
Initial triage shows a handful of dependencies and code paths that need to be
updated to support a successful build. Most components in the core framework
and standard extensions appear to run on Java 17. Efforts to eliminate illegal
reflective access warnings under Java 11 provide some pointers to potential
blockers for Java 17.
Successful completion should include updating the GitHub automated workflow for
regular builds on Java 17. Completion may not include resolving every issue
related to Java 17, but it should include a successful build of all project
elements.
was:
17, the next LTS version of Java, has been released. NiFi should support
running on it. A week or two ago, I tried and NiFi wouldn't start when 17 was
used.
This may need to wait for NiFi version 2 when Java 11 will be minimum supported
Java version. But, an attempt to support 8,11,and 17 can be made. Perhaps build
with 17 but target 8.
> Support Java 17
> ---------------
>
> Key: NIFI-9280
> URL: https://issues.apache.org/jira/browse/NIFI-9280
> Project: Apache NiFi
> Issue Type: Improvement
> Reporter: Andrew Atwood
> Assignee: David Handermann
> Priority: Major
>
> 17, the next LTS version of Java, has been released. NiFi should support
> running on it. A week or two ago, I tried and NiFi wouldn't start when 17 was
> used.
> This may need to wait for NiFi version 2 when Java 11 will be minimum
> supported Java version. But, an attempt to support 8,11,and 17 can be made.
> Perhaps build with 17 but target 8.
> Initial triage shows a handful of dependencies and code paths that need to be
> updated to support a successful build. Most components in the core framework
> and standard extensions appear to run on Java 17. Efforts to eliminate
> illegal reflective access warnings under Java 11 provide some pointers to
> potential blockers for Java 17.
> Successful completion should include updating the GitHub automated workflow
> for regular builds on Java 17. Completion may not include resolving every
> issue related to Java 17, but it should include a successful build of all
> project elements.
--
This message was sent by Atlassian Jira
(v8.20.1#820001)
