This is a follow-up to JENKINS-55562.
Once JENKINS-55575 is integrated into Lib Version Number, we can use new generic classes for robust Java version comparison in the core. It should prevent issues if any other plugin ships something unexpected in the metadata (like "8" instead of "1.8")
Originally reported by 
oleg_nenashev, imported from: Make Jenkins tolerant against incorrect minimum Java version specifications in plugin metadata
- assignee: oleg_nenashev
- status: Resolved
- priority: Minor
- component(s): core
- label(s): java11
- resolution: Fixed
- resolved: 2019-02-12T09:25:21+00:00
- votes: 0
- watchers: 1
- imported: 2025-11-24
Raw content of original issue
This is a follow-up to JENKINS-55562.
Once JENKINS-55575 is integrated into Lib Version Number, we can use new generic classes for robust Java version comparison in the core. It should prevent issues if any other plugin ships something unexpected in the metadata (like "8" instead of "1.8")
This is a follow-up to
JENKINS-55562.Once
JENKINS-55575is integrated into Lib Version Number, we can use new generic classes for robust Java version comparison in the core. It should prevent issues if any other plugin ships something unexpected in the metadata (like "8" instead of "1.8")Originally reported by
oleg_nenashev, imported from: Make Jenkins tolerant against incorrect minimum Java version specifications in plugin metadata
Raw content of original issue