Configure project to explicitly use JDK 11 for IntelliJ recognition#84
Merged
Configure project to explicitly use JDK 11 for IntelliJ recognition#84
Conversation
Co-authored-by: ehmkah <6233328+ehmkah@users.noreply.github.com>
Co-authored-by: ehmkah <6233328+ehmkah@users.noreply.github.com>
Copilot
AI
changed the title
[WIP] Configure this project that intellij knows it should use jdk11
Configure project to explicitly use JDK 11 for IntelliJ recognition
Jul 2, 2025
Owner
|
Please add an entry to changelog what you changed |
Co-authored-by: ehmkah <6233328+ehmkah@users.noreply.github.com>
Contributor
Author
Added changelog entry for the Gradle build configuration changes in commit c2807e2. |
ehmkah
approved these changes
Jul 2, 2025
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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 PR configures the Gradle build to explicitly specify JDK 11 requirements, ensuring IntelliJ IDEA and other IDEs properly recognize and use the correct Java version when importing the project.
Changes Made
build.gradle
gradle.properties (new file)
README.adoc
Benefits
The project has been using Java 11 since version 1.8.0 (as noted in CHANGELOG.md), but the build configuration didn't explicitly enforce this requirement. These changes make the Java 11 dependency explicit and automatic.
Fixes #83.
Warning
Firewall rules blocked me from connecting to one or more addresses
I tried to connect to the following addresses, but was blocked by firewall rules:
cache-redirector.jetbrains.com/usr/lib/jvm/temurin-17-jdk-amd64/bin/java --add-opens java.base/java.util=ALL-UNNAMED --add-opens java.base/java.lang=ALL-UNNAMED --add-opens java.base/java.lang.invoke=ALL-UNNAMED --add-opens java.base/java.util=ALL-UNNAMED --add-opens java.prefs/java.util.prefs=ALL-UNNAMED --add-opens java.prefs/java.util.prefs=ALL-UNNAMED --add-opens java.base/java.nio.charset=ALL-UNNAMED --add-opens java.base/java.net=ALL-UNNAMED --add-opens java.base/java.util.concurrent.atomic=ALL-UNNAMED -XX:MaxMetaspaceSize=256m -XX:+HeapDumpOnOutOfMemoryError -Xms256m -Xmx512m -Dfile.encoding=UTF-8 -Duser.country -Duser.language=en -Duser.variant -cp /home/REDACTED/.gradle/wrapper/dists/gradle-7.2-bin/2dnblmf4td7x66yl1d74lt32g/gradle-7.2/lib/gradle-launcher-7.2.jar org.gradle.launcher.daemon.bootstrap.GradleDaemon 7.2(dns block)If you need me to access, download, or install something from one of these locations, you can either:
💬 Share your feedback on Copilot coding agent for the chance to win a $200 gift card! Click here to start the survey.