Do not activate org.eclipse.jdt.ui.javaEditorScope from JavaStackTracePageParticipant - #978
Conversation
There was a problem hiding this comment.
Pull request overview
Removes activation of the Java editor context (org.eclipse.jdt.ui.javaEditorScope) from JavaStackTracePageParticipant so that, when a JavaStackTraceConsolePage is active in the Console view, it no longer masks keybindings contributed specifically for the Console view context (per issue #977).
Changes:
- Stops activating
org.eclipse.jdt.ui.javaEditorScopewhen the Java stack trace console page is activated. - Removes the corresponding context deactivation logic and unused context-service imports/field.
💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.
|
Note: this change will remove See jdt.ui which contributes this: I believe (not tested) instead of removing usage of Java editor scope, you can define Java Console scope and contribute similar key to the jdt.debug.ui plugin.xml |
2d5af92 to
8c33f6b
Compare
Thanks for this proposal. This works like a charm. |
iloveeclipse
left a comment
There was a problem hiding this comment.
Please update text as proposed, beside this looks good.
iloveeclipse
left a comment
There was a problem hiding this comment.
Identifier should be fixed
JavaStackTracePageParticipant. This will mask the ConsoleView context when JavaStackTraceConsolePage is active in ConsoleView. Create own context for Console View. see eclipse-jdt#977
8c33f6b to
70eba3f
Compare
|
Fixed all the comments. |
This will mask the ConsoleView context when JavaStackTraceConsolePage is active in ConsoleView.
see #977