Skip to content

Showing a preview of the target state in the editor#1937

Merged
laeubi merged 2 commits intoeclipse-pde:masterfrom
laeubi:show_resolve_state_in_editor
Sep 4, 2025
Merged

Showing a preview of the target state in the editor#1937
laeubi merged 2 commits intoeclipse-pde:masterfrom
laeubi:show_resolve_state_in_editor

Conversation

@laeubi
Copy link
Contributor

@laeubi laeubi commented Aug 20, 2025

Currently if one loads a target not using the planner mode there is no guarantee setting it will actually lead to a satisfiable solution. And even with planner mode there are cases where P2 can get to a different result than a real OSGi resolution or there are location types that do not resolve at all. So currently one is forced to actually set the target platform, then look at the target platform state view, identify the problem, change something and start again.

This aims to add a new tab "Resolved State" that shows the resolved state of the bundles that would be set as a result of activate the current target platform.

@github-actions
Copy link

github-actions bot commented Aug 20, 2025

Test Results

   765 files  ±0     765 suites  ±0   58m 53s ⏱️ + 9m 50s
 3 611 tests ±0   3 556 ✅ ±0   54 💤 ±0  1 ❌ ±0 
10 833 runs  ±0  10 669 ✅ ±0  163 💤 ±0  1 ❌ ±0 

For more details on these failures, see this check.

Results for commit 117567a. ± Comparison against base commit 6f0d306.

♻️ This comment has been updated with latest results.

@laeubi laeubi force-pushed the show_resolve_state_in_editor branch 2 times, most recently from 9eb3178 to a54fd81 Compare August 21, 2025 13:45
@laeubi laeubi marked this pull request as ready for review August 21, 2025 13:46
@laeubi
Copy link
Contributor Author

laeubi commented Aug 21, 2025

This is now ready to be merged once master is open.

Currently if one loads a target not using the planner mode there is no
guarantee setting it will actually lead to a satisfiable solution. And
even with planner mode there are cases where P2 can get to a different
result than a real OSGi resolution or there are location types that do
not resolve at all. So currently one is forced to actually set the
target platform, then look at the target platform state view, identify
the problem, change something and start again.

This aims to add a new tab "Resolved State" that shows the resolved
state of the bundles that would be set as a result of activate the
current target platform.
@laeubi laeubi force-pushed the show_resolve_state_in_editor branch from a54fd81 to 73c6162 Compare September 4, 2025 04:39
@eclipse-pde-bot
Copy link
Contributor

This pull request changes some projects for the first time in this development cycle.
Therefore the following files need a version increment:

ui/org.eclipse.pde.ui/META-INF/MANIFEST.MF

An additional commit containing all the necessary changes was pushed to the top of this PR's branch. To obtain these changes (for example if you want to push more changes) either fetch from your fork or apply the git patch.

Git patch
From d1e1ae2b28fe6e66c86eb750cb67d0d70d02cfd8 Mon Sep 17 00:00:00 2001
From: Eclipse PDE Bot <pde-bot@eclipse.org>
Date: Thu, 4 Sep 2025 04:46:10 +0000
Subject: [PATCH] Version bump(s) for 4.38 stream


diff --git a/ui/org.eclipse.pde.ui/META-INF/MANIFEST.MF b/ui/org.eclipse.pde.ui/META-INF/MANIFEST.MF
index 69ac002d3d..f8db32e0c6 100644
--- a/ui/org.eclipse.pde.ui/META-INF/MANIFEST.MF
+++ b/ui/org.eclipse.pde.ui/META-INF/MANIFEST.MF
@@ -2,7 +2,7 @@ Manifest-Version: 1.0
 Bundle-ManifestVersion: 2
 Bundle-Name: %name
 Bundle-SymbolicName: org.eclipse.pde.ui; singleton:=true
-Bundle-Version: 3.16.200.qualifier
+Bundle-Version: 3.16.300.qualifier
 Bundle-Activator: org.eclipse.pde.internal.ui.PDEPlugin
 Bundle-Vendor: %provider-name
 Bundle-Localization: plugin
-- 
2.51.0

Further information are available in Common Build Issues - Missing version increments.

@laeubi laeubi merged commit a1f7257 into eclipse-pde:master Sep 4, 2025
17 of 19 checks passed
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