Skip to content

Add Select Required and Remove Unresolved actions to validation dialog#2351

Open
vogella wants to merge 1 commit into
eclipse-pde:masterfrom
vogella:remove-unresolved-plugins-button
Open

Add Select Required and Remove Unresolved actions to validation dialog#2351
vogella wants to merge 1 commit into
eclipse-pde:masterfrom
vogella:remove-unresolved-plugins-button

Conversation

@vogella
Copy link
Copy Markdown
Contributor

@vogella vogella commented Jun 1, 2026

The plug-in validation dialog (opened by the Validate Plug-ins button on a launch configuration's Plug-ins/Bundles tab) now offers two in-place fixes. Select Required adds the missing required plug-ins, and Remove Unresolved unchecks every plug-in whose bundle did not resolve, repeating validation so transitively broken plug-ins are handled in one click. This removes the manual cleanup the issue describes, since you can fix the selection directly from the list that reports the problems.

Both actions validate the tree's current selection (not the persisted configuration) so the dialog refreshes to reflect the change, and the tab is marked dirty so it can be applied. The buttons are opt-in, so the dialog shown at launch time, where there is no tree to modify, is unaffected; Remove Unresolved is offered only for plug-in/bundle launches, not feature-based ones.

Fixes #2323

@github-actions
Copy link
Copy Markdown

github-actions Bot commented Jun 1, 2026

Test Results

  126 files  ±0    126 suites  ±0   36m 51s ⏱️ + 1m 0s
3 512 tests +2  3 458 ✅ +2   54 💤 ±0  0 ❌ ±0 
9 339 runs  +6  9 209 ✅ +6  130 💤 ±0  0 ❌ ±0 

Results for commit aa47988. ± Comparison against base commit 14ab8d4.

♻️ This comment has been updated with latest results.

The plug-in validation dialog (shown by the "Validate Plug-ins" button
on the launch configuration's Plug-ins/Bundles tab) now offers two
in-place fixes for the reported problems:

* Select Required adds the missing required plug-ins/features.
* Remove Unresolved unchecks every plug-in whose bundle did not
  resolve, matched by symbolic name and version. Validation is repeated
  against the new checked set after each pass, so plug-ins that only
  become unresolved once a dependency has been removed are handled in
  the same click.

Both actions validate the tree's current (unsaved) selection rather than
the persisted launch configuration, so the dialog refreshes to reflect
the change, and the tab is marked dirty so the change can be applied.
The dialog clears to a "no problems" entry once all issues are fixed.

The buttons are opt-in via PluginStatusDialog.setActions(), so the
dialog shown at launch time (where there is no plug-in tree to modify)
is unaffected. Remove Unresolved is offered only for plug-in/bundle
launches, not for feature-based launches.

Fixes eclipse-pde#2323
@vogella vogella force-pushed the remove-unresolved-plugins-button branch from abf0ec5 to aa47988 Compare June 2, 2026 11:50
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.

Add option to remove "unresolved" bundles from launch configuration

1 participant