gradle is no longer available as an RPM package since fedora 31.
The version that is available up to fedora 30 is 4.4.1, which was released in December 2017, which was already out of date when fedora 30 was released.
Gradle was then removed from fedora 31 and later because:
- it failed to build, and it also failed to build itself, even in “bootstrap” mode
- updating to newer versions was/is basically impossible
Some people (myself included) tried to fix gradle, update it to a newer version, and add it back to fedora, but with the way the build system works, I see no way for this ever to become possible again:
- even their source code downloads contain and need a prebuilt JAR to launch the build process,
- the build process needs internet access to download all their dependencies (with fixed versions)
We have not even found a way to make the official gradle release binaries build gradle itself without internet access, let alone have a working self-built gradle.
When trying to communicate our frustrations with the gradle build process to the gradle project, we were basically ridiculed, and told that “we’re just not doing it right”, and that they need their bespoke build process (which, as I mentioned, can’t be made to run “ab initio”, and downloads loads of stuff from the internet, even when you download their “complete release”) for “reproducibility”. They even got angry with me when I mentioned that it might be argued that gradle is not an open source project then, if nobody but themselves can even build it 
Which is the point at which we gave up.
This is why we now recommend packagers to use maven when possible, or to do simple ports from gradle to maven for necessary projects, where this is feasible. Some packages have been doing this for a while (including junit5).