Drop JDK 11 support

[andsel]

Release notes

Remove support for JDK 11

What does this PR do?

Updates the jvm.options and JvmOptionsParser to remove support for JDK 11. If the options parser identifies that the running JVM is less than 17, it refuses to start.

Why is it important/What is the impact to the user?

If a user runs Logstash with a hosted JDK and not the one bundled with Logstash distribution, like setting a specific LS_JAVA_HOME, which is minor than JDK 17 then Logstash refuses to start. Has to provide at least a JDK 17 or unset the LS_JAVA_HOME and let Logstash uses the bundled JDK.

Checklist

• My code follows the style guidelines of this project
• [ ] I have commented my code, particularly in hard-to-understand areas
• I have made corresponding changes to the documentation
• I have made corresponding change to the default configuration files (and/or docker env variables)
• [ ] I have added tests that prove my fix is effective or that my feature works

Author's Checklist

• try with sdkman and a JDK 11

How to test this PR locally

Related issues

Use cases

Screenshots

Logs

[jsvd]

Please check Java version references in

• https://github.com/elastic/logstash/blob/main/logstash-core/lib/logstash/runner.rb#L321-L323
• https://github.com/elastic/logstash/blob/main/docs/static/running-logstash-windows.asciidoc?plain=1#L49-L58
• https://github.com/elastic/logstash/blob/main/logstash-core/locales/en.yml#L443-L448

[jsvd]

Minor tweaks, otherwise LGTM

[elastic-sonarqube]

Quality Gate passed

Issues
0 New issues
0 Fixed issues
0 Accepted issues

Measures
0 Security Hotspots
No data about Coverage
No data about Duplication

See analysis details on SonarQube

[elasticmachine]

💚 Build Succeeded

• Buildkite Build
• Commit: adba7cd

History

• 💚 Build #1473 succeeded e18bca7
• 💚 Build #1472 succeeded 20533ee
• 💚 Build #1470 succeeded 9c127ca
• 💔 Build #1457 failed 24b59cd

cc @andsel