chore: use java.release=8 when building pgjdbc from the generated source distribution #3038
Conversation
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
…rce distribution Previously, pom.xml used source=1.8, target=1.8 so it might produce invalid bytecode when running on Java 1.8 Now pom.xml would use --release 8 to avoid such issues. See pgjdbc#3014
redalogobject
pushed a commit
to logobject/pgjdbc
that referenced
this pull request
Dec 7, 2023
…rce distribution (pgjdbc#3038) Previously, pom.xml used source=1.8, target=1.8 so it might produce invalid bytecode when running on Java 1.8 Now pom.xml would use --release 8 to avoid such issues. See pgjdbc#3014
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.
Previously, pom.xml used source=1.8, target=1.8 so it might produce invalid bytecode when running on Java 1.8
Now pom.xml would use --release 8 to avoid such issues.
See #3014