On Sat, Apr 27, 2024 at 1:24 AM Valentin Delaye (jonesbusy) < [email protected]> wrote:
> 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 ? > Yes, that's expected because no Jenkins core version requires Java 17 as its minimum Java version. > - Does this mean the plugin need a Java 17 runtime or only for compile ? > I believe that when you set maven.compiler.release to 17, it is generating Java 17 byte code. That will require Java 17 at runtime. > - Show I rollback until the toolchain is adapted for Java 17 ? > I would rollback until the toolchain supports Java 17 later this year. It might be in the weekly release as early as July or August. Mark Waite -- 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/CAO49JtEF1R%3DP52_%2BBQaDKLoD8ymByv_5jB54E1J4ambyM7PftA%40mail.gmail.com.
