On Tue, Jun 4, 2024 at 5:21 PM Basil Crow <[email protected]> wrote: > By creating a backport branch of the test harness that > continues to be based on Java 11 bytecode, and using this backport > branch in the plugin parent POM until we decide to drop Java 11 > support in the plugin parent POM (most likely around the timeframe > when Jetty 12 EE 9 is delivered in LTS). This means that every change > to the test harness will need to be backported to become available to > plugin parent POM releases—painful in the short term, but the idea is > that this phase will not last more than a few months.
With today's release of 2.463, the default branch of the test harness is now targeting 2.463 and Java 17 or newer. I have created a 2225.x backport branch that still targets 2.361 and Java 11 or newer. The plugin POM will still support Java 11 for a bit longer, so test harness changes should generally be backported to this branch in the short term. Let me know if you need help doing this. https://github.com/jenkinsci/jenkins-test-harness/pull/762 and https://github.com/jenkinsci/jenkins-test-harness/pull/770, both targeting the default branch of the test harness, add EE 8 and EE 9 support (respectively). These PRs will not be backported; rather, they will form the basis of a future plugin POM release that requires Java 17 or newer and Jetty 12 or newer. -- You received this message because you are subscribed to the Google Groups "Jenkins Developers" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-dev/CAFwNDjpww0sQgHW2TPfBxGhyL2RhG%2B_%2B%2BaPDD%2BfyQiXXe8J9YA%40mail.gmail.com.
