It appears that javapackages-tools has some hardcoded dependencies specific version of the JDK at any given time.

There are two problems with that however, one is that the version picked is usually not coordinated with the OpenJDK team, causing a lot of additional work when there is a version mismatch (see for example handling of RHEL 10 default JDK to be OpenJDK 21 instead of 17), and the other being that if the system JDK changes for any reason but javapackages-tools is not updated, any java application or library that depends on javapackages-tools will silently use the older JDK failing in unexpected ways and opening the doors to CVEs and other problems for our customers and users.

Javapackage-tools should not depend on a specific version of the JDK and instead respect the system configurations (i.e. OpenJDK packages using default java and java-devel provides), and should definitely not pick at any time a random JDK without consulting with the OpenJDK team.