Deal with unsupported target options in compiler preferences #1572
Conversation
This file contains 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
After we dropped support of Java < 1.8 compliance level, we still have to deal with projects that have these setting stored in preferences. - Make sure we don't allow use unsupported compliance from JRE < 1.8 - Make sure we update value of compliance/source and target to first supported version See eclipse-jdt#1465
|
Before change Considering existing Java 1.7 project settings, following will be shown and after "Apply" all values would be set to 1.7 (even if they show 1.8):
After change
|
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.
After we dropped support of Java < 1.8 compliance level, we still have to deal with projects that have these setting stored in preferences.
See #1465