[
https://issues.apache.org/jira/browse/CAMEL-22996?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Aurélien Pupier updated CAMEL-22996:
------------------------------------
Description:
As part of the big work leading up to SB4 and what else, then its worth to
consider dropping Java 17 and let 21 be primary supported and also the minimum
version.
There is no bandwidth to support 17, 21, and 25. Camel only officially support
at most 2 LTS java versions.
To reopen when upgraded https://github.com/apache/camel/pull/24299
first iteration plan:!
* update minimal Java version in pom file
* check if there are specific Java 17 Maven profiles and i they are still
relevant
* remove Java 17 on CI jobs (both Jenkins and GitHub)
* remove specific maven enforcer skip
* on GitHub actions, this is not a complete removal, it needs to be replaced
by JDK 21, to ensure that we have oldest and newest LTS tested
* ensure Javadoc is working and pointing to JDK 21 as base
* Check tests with @EnabledForJreRange , if there are some with Max
JRE_JAVA_17, to remove the tests. And remove annotation min java 21
* check place with reflection code where it was done because there was jdk 17
missing functions
* update readmes and documentations
* add a top-level breaking change note in upgrade guide
keep for separate iterations:
* upgrade of libraries inthe issue links which are requiring JDK 21. For each
of them, first try to reopen associated PR to reactivate Dependabot on them.
And then see if manual changes are also required
was:
As part of the big work leading up to SB4 and what else, then its worth to
consider dropping Java 17 and let 21 be primary supported and also the minimum
version.
There is no bandwidth to support 17, 21, and 25. Camel only officially support
at most 2 LTS java versions.
To reopen when upgraded https://github.com/apache/camel/pull/24299
> Drop Java 17 so Java 21 is minimum and primary supported
> --------------------------------------------------------
>
> Key: CAMEL-22996
> URL: https://issues.apache.org/jira/browse/CAMEL-22996
> Project: Camel
> Issue Type: Task
> Components: build system
> Reporter: Claus Ibsen
> Assignee: Aurélien Pupier
> Priority: Major
> Fix For: 4.24.0
>
>
> As part of the big work leading up to SB4 and what else, then its worth to
> consider dropping Java 17 and let 21 be primary supported and also the
> minimum version.
> There is no bandwidth to support 17, 21, and 25. Camel only officially
> support at most 2 LTS java versions.
> To reopen when upgraded https://github.com/apache/camel/pull/24299
> first iteration plan:!
> * update minimal Java version in pom file
> * check if there are specific Java 17 Maven profiles and i they are still
> relevant
> * remove Java 17 on CI jobs (both Jenkins and GitHub)
> * remove specific maven enforcer skip
> * on GitHub actions, this is not a complete removal, it needs to be
> replaced by JDK 21, to ensure that we have oldest and newest LTS tested
> * ensure Javadoc is working and pointing to JDK 21 as base
> * Check tests with @EnabledForJreRange , if there are some with Max
> JRE_JAVA_17, to remove the tests. And remove annotation min java 21
> * check place with reflection code where it was done because there was jdk 17
> missing functions
> * update readmes and documentations
> * add a top-level breaking change note in upgrade guide
> keep for separate iterations:
> * upgrade of libraries inthe issue links which are requiring JDK 21. For each
> of them, first try to reopen associated PR to reactivate Dependabot on them.
> And then see if manual changes are also required
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
