Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This pull request adds support for Fedora/RPM-based distributions and updates the Java version requirement across the project from Java 8 to Java 17. It introduces a new RPM packaging workflow, updates documentation and build scripts accordingly, and ensures the application and its packages depend on Java 17 or newer.
Fedora/RPM Packaging Support:
package-rpm.shto automate building RPM packages for Fedora, RHEL, CentOS, and similar distributions. This script builds the JAR, prepares the RPM build environment, and creates the.rpmpackage.fedora-package/SPECS/numberguessinggame.specand supporting.gitignorefor build artifacts. The spec defines installation details, dependencies, and a wrapper script for launching the game. [1] [2].rpmfiles as release artifacts. [1] [2]Documentation Updates:
README.mdwith installation and uninstallation instructions for Fedora/RPM-based systems, including example commands and download links. [1] [2].debfilename.Java Version Upgrade:
README.md, build scripts (package-linux.sh,package-macos.sh,package-win.sh), and Gradle configuration. [1] [2] [3] [4] [5]Build and Dependency Management:
app/build.gradlefile, removing outdated comments and ensuring compatibility with the new Java version. [1] [2]These changes collectively improve cross-distribution support, modernize the codebase for Java 17, and streamline the packaging and release process.