I’ll note the illegal reflection is only an issue starting with Java 16, and that can be “fixed” with some add-opens CLI options to Java. See for example how the ErrorProne compiler plugin requires several of those flags in a build with recent Java versions (and I’d expect similar for Lombok and other projects that access JDK internals).
— Matt Sicker > On Jan 4, 2022, at 09:34, Basil Crow <m...@basilcrow.com> wrote: > > On Mon, Jan 3, 2022 at 12:48 PM Mark Waite <mark.earl.wa...@gmail.com> wrote: >> >> I think there are changes that are as yet undiscovered on the removal of >> Java 8 support. I believe that finding and fixing those surprises will need >> more time. > > We are already aware of issues with WebSockets (fixed), JAXB (fixed in > all but the least used plugins), Linux agent installers (nobody seems > to care), and illegal reflective access warnings (not blocking). I > doubt we will discover many new issues with switching the _runtime_ to > Java 11 in any but the least used plugins. > > On the other hand, switching _builds_ and _tests_ to Java 11 does > often require the usual plugin refresh process: updating the plugin > parent POM and plugin BOM, dealing with Enforcer, updating the > Jenkinsfile, adjusting annotations, tweaking mocks, suppressing > SpotBugs false positives that only show up on Java 11, triaging > miscellaneous test failures, etc. This seems to be the majority of the > remaining work, but it does not affect end users. > > I am not sure that additional time will incentivize the completion of > the remaining work, whether it be production changes to long-tail > plugins or build metadata updates. If a plugin is unmaintained or its > maintainer has not yet refreshed it by June 2022, I doubt that this > status will change by September 2022. If anything, delaying the > release until September may (ironically) decrease the perceived need > to take action on the part of plugin maintainers. > > My point is not that risk does not exist, but that additional time is > not likely to reduce risk. Therefore, I see no reason to wait until > September. > > -- > 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/CAFwNDjpespJqVCcHCqGUVK4QUQvv1UPd3Y%2BtM%2B2Ek5Hq39-rBA%40mail.gmail.com. -- 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/870E34A5-9F72-4CAA-A00F-B03E7BA04CC6%40gmail.com.
