Skip to content

Hard dependency on a specific java version causes warning of deprecated runtime

Description:

Looks like the package has a strict dependency on Java version, currently 17. As of the last update, there is a warning that support for Java 17 will end next March. While this makes this issue a very low priority, for a while Jenkins has been the only package on my system that required Java 17 next to 21 and 24, despite Jenkins officially supporting Java 21 since around it's release. Maybe it's a worthwhile improvement to accept any java version supported by upstream? I am not sure if it's feasible as I have very little experience with packaging, and I see the systemd unit would have to be generated in a more dynamic fashion.

Chances are I reported this in a less than optimal channel, as nothing is breaking currently, but I felt like some context and feedback might help, sorry about that. Please feel free to point me to the correct direction I can follow next time.

Additional info:

To upload designs, you'll need to enable LFS and have an admin enable hashed storage. More information