The problem is Java packages are converged around the Maven central repository which is not compatible with the RPM way of doing things. (it's a packaging mess

The problem is Java packages are converged around the Maven central repository which is not compatible with the RPM way of doing things. (it's a packaging mess somewhat halfway between RPM and NodeJS...) Since most Java developers use something other than an RPM based packaging system (hey, it runs anywhere ;) they simply don't care about it which pushes the impossible job of creating native packages for 2,5 million Maven central packages to a maintainer. You don't need a maintainer to fix that mess, you need an army or accept sometimes it's more opportunistic to use soms non-native technology.