On Tue, Mar 29, 2022 at 10:25 PM 'Daniel Beck' via Jenkins Developers
> Seems reasonable if really unused.
Thanks. Of course I will verify this systematically before proposing the PRs.
> 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.