You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Is your feature request related to a problem? Please describe.
The OpenSearch uses at least 4 different JDK versions at the different stages of build process: 8, 11, 14 and 15. While 8/11/14 have to be preinstalled by user / developer, the JDK-15 distribution [1] is fetched from the AdoptOpenJDK project, which is not supported anymore and has moved to Eclipse Foundation under Adoptium project [2]. Both 14 and 15 are effectively dead and are superseded by JDK-17 LTS [3] release.
Describe the solution you'd like
Reduce the number of required JDK versions to 8, 11 and 17. Use the Adoptium distributions as bundled JDK version to run tests (ideally, we should end up with 8 and 17 but 11 is still used widely).
Describe alternatives you've considered
Keep things as-is.
Additional context
JDK-17 is the next LTS release. The expectations are that OpenSearch should be able to run under JDK-17 and benefit from a number of performance and security improvements. The quite an impaction change for OpenSearch project is deprecation of the SecurityManager (JEP-411), so the JVM issues following warnings:
WARNING: System::setSecurityManager will be removed in a future release
Use JDK-17 as bundled JDK distribution to run tests
Update JDK-14 requirement, switch to JDK-17 instead (update DEVELOPER.md): since the decision was made to not backport Lower build requirement from Java 14+ to Java 11+ #940 to 1.x, the bwc tests would still require JDK-14 to build 1.x/1.0
Update Jenkins pipelines to pick the JDK version for each branch (11 / 17 or 14 for 1.x/1.0)
reta
changed the title
Modernize and consolidate JDKs usage accross all stages of the build
Modernize and consolidate JDKs usage across all stages of the build
Oct 8, 2021
I think your plan is good. My 0.02c is that we should be building and packaging all official bits with 11, and testing on 8, 11 and 17. I'm good with developers using 17.
Is your feature request related to a problem? Please describe.
The
OpenSearch
uses at least 4 different JDK versions at the different stages of build process: 8, 11, 14 and 15. While 8/11/14 have to be preinstalled by user / developer, the JDK-15 distribution [1] is fetched from the AdoptOpenJDK project, which is not supported anymore and has moved to Eclipse Foundation under Adoptium project [2]. Both 14 and 15 are effectively dead and are superseded by JDK-17 LTS [3] release.[1] https://github.com/opensearch-project/OpenSearch/blob/main/buildSrc/version.properties
[2] https://adoptium.net/
[3] https://openjdk.java.net/projects/jdk/17/
Describe the solution you'd like
Reduce the number of required JDK versions to 8, 11 and 17. Use the Adoptium distributions as bundled JDK version to run tests (ideally, we should end up with 8 and 17 but 11 is still used widely).
Describe alternatives you've considered
Keep things as-is.
Additional context
JDK-17 is the next LTS release. The expectations are that OpenSearch should be able to run under JDK-17 and benefit from a number of performance and security improvements. The quite an impaction change for OpenSearch project is deprecation of the SecurityManager (JEP-411), so the JVM issues following warnings:
bwc
tests would still require JDK-14 to build 1.x/1.0The text was updated successfully, but these errors were encountered: