So if you only rely in things like OpenJDK (like for running
Minecraft, as I do, too), then you'll be fine.
If you need ant or maven, you should be fine too, since those two (and
their dependencies) will continue to be maintained.
But everything else ... *tumbleweeds*
Just one user's snapshot; On a not-atypical dev-box here, installed java apps are
PHPStorm (upstream snap)
IntelliJ* (upstream snap)
Eclipse (upstream tarball)
DBeaver-CE (upstream rpm)
android-studio (upstream)
In dev-user cases, any additional 'needed' apps are typically getting installed
from upstreams -- as tarballs, snaps, flatpaks, or rpms. Seldom, if ever, from Fedora
pkgs.
and pkgs
rpm -qa | egrep -i "java|jdk|mvn|maven" | sort
copy-jdk-configs-4.0-1.fc34.noarch
java-11-openjdk-11.0.12.0.7-4.fc34.x86_64
java-11-openjdk-devel-11.0.12.0.7-4.fc34.x86_64
java-11-openjdk-headless-11.0.12.0.7-4.fc34.x86_64
java-latest-openjdk-17.0.0.0.35-1.rolling.fc34.x86_64
java-latest-openjdk-devel-17.0.0.0.35-1.rolling.fc34.x86_64
java-latest-openjdk-headless-17.0.0.0.35-1.rolling.fc34.x86_64
javapackages-filesystem-5.3.0-15.fc34.noarch
javapackages-tools-5.3.0-15.fc34.noarch
maven-3.6.3-8.fc34.noarch
maven-archiver-3.5.1-1.fc34.noarch
maven-artifact-2.2.1-67.fc34.noarch
maven-artifact-transfer-0.11.0-5.fc34.noarch
maven-common-artifact-filters-3.1.1-1.fc34.noarch
maven-compiler-plugin-3.8.1-8.fc34.noarch
maven-dependency-tree-3.0.1-6.fc34.noarch
maven-doxia-core-1.9.1-4.fc34.noarch
maven-doxia-logging-api-1.9.1-4.fc34.noarch
maven-doxia-module-apt-1.9.1-4.fc34.noarch
maven-doxia-module-fml-1.9.1-4.fc34.noarch
maven-doxia-module-xdoc-1.9.1-4.fc34.noarch
maven-doxia-module-xhtml-1.9.1-4.fc34.noarch
maven-doxia-module-xhtml5-1.9.1-4.fc34.noarch
maven-doxia-sink-api-1.9.1-4.fc34.noarch
maven-doxia-sitetools-1.9.2-4.fc34.noarch
maven-file-management-3.0.0-12.fc34.noarch
maven-filtering-3.2.0-2.fc34.noarch
maven-jar-plugin-3.2.0-5.fc34.noarch
maven-lib-3.6.3-8.fc34.noarch
maven-model-2.2.1-67.fc34.noarch
maven-plugin-bundle-4.2.1-4.fc34.noarch
maven-reporting-api-3.0-21.fc34.noarch
maven-resolver-api-1.4.2-5.fc34.noarch
maven-resolver-connector-basic-1.4.2-5.fc34.noarch
maven-resolver-impl-1.4.2-5.fc34.noarch
maven-resolver-spi-1.4.2-5.fc34.noarch
maven-resolver-transport-wagon-1.4.2-5.fc34.noarch
maven-resolver-util-1.4.2-5.fc34.noarch
maven-resources-plugin-3.2.0-2.fc34.noarch
maven-shared-incremental-1.1-21.fc34.noarch
maven-shared-io-3.0.0-12.fc34.noarch
maven-shared-utils-3.2.1-0.8.fc34.noarch
maven-source-plugin-3.2.1-4.fc34.noarch
maven-surefire-3.0.0~M4-1.fc34.noarch
maven-surefire-plugin-3.0.0~M4-1.fc34.noarch
maven-surefire-provider-junit-3.0.0~M4-1.fc34.noarch
maven-toolchain-2.2.1-67.fc34.noarch
maven-wagon-file-3.4.2-1.fc34.noarch
maven-wagon-http-3.4.2-1.fc34.noarch
maven-wagon-http-shared-3.4.2-1.fc34.noarch
maven-wagon-provider-api-3.4.2-1.fc34.noarch
system-switch-java-1.1.8-5.fc34.noarch
tzdata-java-2021a-1.fc34.noarch
xz-java-1.8-10.fc34.noarch
everything ELSE gets built locally -- either per-machine, or on our in-house
distro/pgg'ing -- as needed.
similarly, on not-atypical non-dev end-user around here,
rpm -qa | egrep -i "java|jdk|mvn|maven" | sort
copy-jdk-configs-4.0-1.fc34.noarch
java-11-openjdk-11.0.12.0.7-4.fc34.x86_64
java-11-openjdk-devel-11.0.12.0.7-4.fc34.x86_64
java-11-openjdk-headless-11.0.12.0.7-4.fc34.x86_64
java-latest-openjdk-17.0.0.0.35-1.rolling.fc34.x86_64
java-latest-openjdk-devel-17.0.0.0.35-1.rolling.fc34.x86_64
java-latest-openjdk-headless-17.0.0.0.35-1.rolling.fc34.x86_64
javapackages-filesystem-5.3.0-15.fc34.noarch
javapackages-tools-5.3.0-15.fc34.noarch
system-switch-java-1.1.8-5.fc34.noarch
tzdata-java-2021a-1.fc34.noarch
and that's mostly it.
And again, in _some_ end-user cases, any 'needed' end-user apps are getting
installed from upstreams -- as tarballs, snaps, flatpaks, or rpms. Seldom, if ever, from
Fedora pkgs.