> Am 27.04.2024 um 09:24 schrieb Valentin Delaye (jonesbusy) > <jonesb...@gmail.com>: > > Hi, > > I'm a bit confused on the minimum required Java version for plugins > > I maintain the https://github.com/jenkinsci/flyway-api-plugin which is an API > plugin for flyway dependencies. > > Since flyway 10 Java 17 is required. > > I open a PR https://github.com/jenkinsci/flyway-api-plugin/pull/9/files > > And changing the > > <maven.compiler.release>17</maven.compiler.release> > <maven.compiler.testRelease>17</maven.compiler.testRelease> > > And tested using bom the plugin against known consumer. No issue found > > However is looks I cannot release the plugin > https://github.com/jenkinsci/flyway-api-plugin/actions/runs/8858031719/job/24326194647 > due to JDK11 used on CD. > > - Is it expected ? > - Does this mean the plugin need a Java 17 runtime or only for compile ? > - Show I rollback until the toolchain is adapted for Java 17 ? >
At least it makes sense to rise an issue for the CD toolchain so this problem will not be forgotten when we switch to Java 17 in September. You can do JDK 17 releases using the manual release process though, an example is available at https://github.com/jenkinsci/autograding-plugin. This plugin also has a dependency to a Java 17 library so I needed to switch to Java a 17 for the plugin as well. Ulli -- 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 jenkinsci-dev+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-dev/3A4518C7-1FD3-4564-8CBE-E2B60C996225%40gmail.com.
