Always show Installable Unit (IU) ID in target editor

[vogella]

Modified StyledBundleLabelProvider to always display the technical ID of Installable Units in the Target Platform Editor's Definition and Content tabs. If a descriptive name exists and differs from the ID, both are shown (Name [ID]), otherwise just the ID is displayed.

Fixes #1432

[github-actions]

Test Results

  147 files  +    4    147 suites  +4   34m 34s ⏱️ + 2m 22s
3 493 tests ±    0  3 439 ✅ +    1   54 💤 ± 0  0 ❌  - 1 
9 303 runs  +2 135  9 173 ✅ +2 112  130 💤 +24  0 ❌  - 1 

Results for commit 37c9cc1. ± Comparison against base commit 3389587.

♻️ This comment has been updated with latest results.

[HannesWell]

This is a difficult one.
On one hand I understand the desire to see the ID and it looks good.
On the other hand the concern from Christoph from #1432 (comment) is also valid.

I have to think about this.
Do others have opinions?

[merks]

Yes, on the downside it's very verbose. It could be shown in a hover instead... It's also significant to note that the ID available directly in the source, whereas the name and the version are not. But the association between the ID in the source versus the arbitrary name is also not shown anywhere currently...

[laeubi]

I just wanted to point out that code annotations are a powerful feature for such purpose as "showing a problem in the source" or even additional information (like the name). And as the target editor already use them (e.g. to provide set as active target) it might maybe be a better alternative for the proposed use-case.

Also a rightclick->show in source would be helpful as well...

[travkin79]

Another idea might be adding a toggle button "export mode" / "simple mode" to the button list next to the locations part in the target editor that would add the desired IDs to the editor's tree view or hide them.

I do also like the idea of having a rightclick->show in source feature.

[eclipse-pde-bot]

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 1a03e632a258fa69f2310770faf061666537c0da Mon Sep 17 00:00:00 2001
From: Eclipse PDE Bot <[email protected]>
Date: Tue, 3 Mar 2026 12:04:42 +0000
Subject: [PATCH] Version bump(s) for 4.40 stream


diff --git a/ui/org.eclipse.pde.ui/META-INF/MANIFEST.MF b/ui/org.eclipse.pde.ui/META-INF/MANIFEST.MF
index 87bb6898ee..ddaa9c6ccc 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.400.qualifier
+Bundle-Version: 3.16.500.qualifier
 Bundle-Activator: org.eclipse.pde.internal.ui.PDEPlugin
 Bundle-Vendor: %provider-name
 Bundle-Localization: plugin
-- 
2.53.0

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