On Wed, Mar 30, 2022 at 7:32 AM Basil Crow <[email protected]> wrote:
> > > 1. IIRC I've seen plugins requiring Java 11 that just don't declare it. > So it's not unused because it isn't needed, but perhaps because plugin > authors are unaware of it? > > I am not familiar with such cases, but I seriously doubt there are > enough of them to justify a subsystem of this complexity. If it is > really the case that some plugin requires a newer JRE at runtime it > can just be documented in the plugin's README rather than with the > elaborate and hard-to-maintain subsystem that is in place now. > > > 2. Will this be replaced by a different system (assuming this is future > proof in principle)? Or will plugins be unable to require higher Java > versions than what their core baseline requires to run? Or will there be > surprises for admins when attempting to install such plugins? I think the > core support for this was essentially a warning in plugin manager. > > Yes the core support for this was essentially a warning in the plugin > manager, and no I am not planning on replacing this with something > else. Plugins will just have to evolve in lockstep with the minimum > Java version required by their core baseline. This is effectively the > case in practice everywhere I've looked, and it also seems like a > reasonable requirement to me > Makes sense. Worst case is that we change our minds a few years down the road and restore this subsystem. And if there's a plugin somewhere that uses this after all, it's basically going to be an unused entry in the Manifest IIRC. +1 and thanks for starting this conversation. (Just in case, I do not think a JEP is needed for what amounts to removal of unused code.) -- 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/CAMo7PtLefPYhzwK%3DvDQeNGy-vJMN1B9%3DTPrbOQ9zHc0MvmH5ew%40mail.gmail.com.
