This issue shapes a plan of updates to apply to `8.19` branch to switch to JRuby 10.0.x ### Phase 1: Create a test branch to align to the latest JRuby `9.4.x`, a significant amount work was done in #17696 and in #17787: - [x] https://github.com/elastic/logstash/pull/19188 - [x] https://github.com/elastic/logstash/issues/19204 - [x] https://github.com/elastic/logstash/issues/19236 ### Phase 2: - [ ] #19237 (evaluate backport of #19010 ). ### Phase 3 - [ ] #19303. Original work for `9.4` migration to `10.0.3` is #18755. Include also the fix for SystemExit in #19017. - [ ] Run the pipeline `logstash-supported-plugins-test-pipeline` on this test branch and check for the original report in #18872. - [ ] migration to `10.0.6` - [ ] https://github.com/elastic/logstash/pull/18856 - [ ] https://github.com/elastic/logstash/pull/18965 - [ ] migration `10.0.5` -> `10.0.6` https://github.com/elastic/logstash/pull/19264
This issue shapes a plan of updates to apply to
8.19branch to switch to JRuby 10.0.xPhase 1:
Create a test branch to align to the latest JRuby
9.4.x, a significant amount work was done in #17696 and in #17787:8.19to jruby 9.4.15 #19204Phase 2:
Phase 3
10.x. #19303. Original work for9.4migration to10.0.3is Bump JRuby to 10.x #18755. Include also the fix for SystemExit in fix forced-shutdown (double SIGINT) behaviour for JRuby 10 #19017.logstash-supported-plugins-test-pipelineon this test branch and check for the original report in Fix plugin test failures caused by JRuby 10 upgrade #18872.10.0.610.0.5->10.0.6Update jruby to 10.0.6.0 #19264