[#60] Avoid deprecation warnings against newer JDT, support Java9 modules#134
Open
[#60] Avoid deprecation warnings against newer JDT, support Java9 modules#134
Conversation
Contributor
|
@szarnekow any idea on how to test this? |
Contributor
Author
I've never used the mwe debug feature pre mwe2 - so unfortunately not. I tried to do a minimal change and mimicked what I found in other subtypes of the launch delegate. |
Contributor
Author
|
@cdietrich Should we still try to fix this? |
Contributor
Author
|
Is this still valuable? |
Contributor
|
I assume we need a solution one day. But am not sure if we already have one with this |
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
2 participants
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.
[#60] Avoid deprecation warnings against newer JDT, support Java9 modules