Skip to content

Modernize and consolidate JDKs usage across all stages of the build #1351

@reta

Description

@reta

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:

WARNING: System::setSecurityManager will be removed in a future release

Metadata

Metadata

Assignees

No one assigned

    Labels

    enhancementEnhancement or improvement to existing feature or request

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions