More customary to IJ error reporting for cases when required JDK is missing #7321
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
dkashyn-sfdc
requested review from
mai93,
ujohnny,
LeFrosch and
agluszak
as code owners
github-actions
bot
added
product: IntelliJ
dkashyn-sfdc
changed the title
dkashyn-sfdc
changed the title
dkashyn-sfdc
changed the title
dkashyn-sfdc
force-pushed
the
report-sync-error
branch
from
9f934be to
521b73f
Compare
|
It is popped more than once but this is only because the plugin ignoring JDK issues and keep going. |
dkashyn-sfdc
force-pushed
the
report-sync-error
branch
from
58adb63 to
d7538f6
Compare
dkashyn-sfdc
force-pushed
the
report-sync-error
branch
from
d7538f6 to
54638ef
Compare
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.
Checklist
Please note that the maintainers will not be reviewing this change until all checkboxes are ticked. See
the Contributions section in the README for more
details.
Discussion thread for this change
Issue number: #7298
Description of this change