Skip to content

chore: ignore deprecated extension warnings in the check and format UIs - #1618

Draft
joaodinissf wants to merge 1 commit into
masterfrom
chore/ignore-deprecated-ui-extensions
Draft

joaodinissf wants to merge 1 commit into
masterfrom
chore/ignore-deprecated-ui-extensions

Conversation

@joaodinissf

Copy link
Copy Markdown
Collaborator

Ignores the 27 deprecation warnings Eclipse reports on org.eclipse.ui.editorActions and org.eclipse.ui.popupMenus in check.ui, checkcfg.ui and xtext.format.ui.

The problem

24 of the warnings are the breakpoint actions from Xtext's XbaseGeneratorFragment2, which writes this block unconditionally, 8 per bundle. The other 3 are the hand-written Deploy and Undeploy menus in check.ui.

These entries are in use. Not Used is the label of the double-click breakpoint toggle, and AbstractTextEditor reads RulerDoubleClick only from editorActions, so moving to commands would need a custom editor and ruler handlers. Xtext has no option to leave the block out, and its own xtend.ide and example projects keep these entries.

The change

Adds .settings/org.eclipse.pde.prefs with compilers.p.deprecated=2 (ignore) to these three projects only, as two of Xtext's example UI projects do. This also hides any other PDE deprecation warning in these three projects. It affects Eclipse only: nothing changes at runtime, and it doesn't reach language authors downstream.

Also bumps the three bundles, as the version baseline check requires.

Testing

  • Eclipse 2026-09 with Temurin 21: on a clean build with other warning fixes applied, all 27 warnings went and none took their place.
  • Maven on this branch, with Temurin 21: clean verify with checkstyle:check, pmd:check, pmd:cpd-check and spotbugs:check passes, including the version baseline check. 451 tests ran with no failures or errors, and 2 were skipped.

🤖 Generated with Claude Code

Eclipse reports 27 warnings on org.eclipse.ui.editorActions and
org.eclipse.ui.popupMenus in these three plugin.xml files. Most are the
breakpoint actions Xtext's XbaseGeneratorFragment2 generates unconditionally,
with no option to leave them out. The double-click breakpoint can't move to
commands without a custom editor, as AbstractTextEditor reads it only from
editorActions. Deploy and Undeploy in check.ui use the same deprecated
mechanism.

Set compilers.p.deprecated to ignore in these three projects only, as two
of Xtext's example UI projects do.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
@joaodinissf
joaodinissf marked this pull request as ready for review November 6, 2026 00:54
@joaodinissf

Copy link
Copy Markdown
Collaborator Author

We're reworking this, so it doesn't need a review as it is. Moving it back to draft.

Posted by Claude Code on behalf of @joaodinissf.

@joaodinissf
joaodinissf removed the request for review from rubenporras November 6, 2026 07:45
@joaodinissf
joaodinissf marked this pull request as draft November 6, 2026 07:45
@rubenporras

Copy link
Copy Markdown
Member

I wonder if this is true. If it is so that Xtext writes block unconditionally that point to deprecated stuff, probably a PR for Xtext is better

This branch has not been deployed

No deployments
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants