> This implies the risk that code could make use of higher level Java APIs and > would compile well, but if this code is running on a lower level java runtime > matching the classes level signature it will fail, since that API does not > exist in the lower level runtime. >
Isn’t this picked up by JEP 247 in javac since Java 11? Or do you have an example that would break with our setup? > For that reason Maven is providing the toolchain plugin. > The toolchain plugin enables to compile with the toolchain specified JDK > version - which can differ from the Maven job runtime JDK. > Same for JUnit testing via surefire plugin. > > Is there a reason why Jenkins POM definitions are not making use of it? > > Kind regards > Markus > > > -- > 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 > <mailto:jenkinsci-dev+unsubscr...@googlegroups.com>. > To view this discussion on the web visit > https://groups.google.com/d/msgid/jenkinsci-dev/1569c8d2-8d74-4a5a-b4d8-4dbd49c39b9cn%40googlegroups.com > > <https://groups.google.com/d/msgid/jenkinsci-dev/1569c8d2-8d74-4a5a-b4d8-4dbd49c39b9cn%40googlegroups.com?utm_medium=email&utm_source=footer>. -- 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/F6E7040A-F372-4C95-AB59-B6BBBF0041C4%40gmail.com.
