Bug 286655 - Make different versions of plug-ins from workspace and target available in the plugin registry
Summary: Make different versions of plug-ins from workspace and target available in th...
Status: CLOSED WONTFIX
Alias: None
Product: PDE
Classification: Eclipse Project
Component: UI (show other bugs)
Version: 3.5   Edit
Hardware: PC Linux
: P3 enhancement (vote)
Target Milestone: ---   Edit
Assignee: PDE-UI-Inbox CLA
QA Contact:
URL:
Whiteboard: stalebug
Keywords: readme
Depends on:
Blocks:
 
Reported: 2009-08-14 11:59 EDT by Curtis Windatt CLA
Modified: 2019-09-09 02:28 EDT (History)
1 user (show)

See Also:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Curtis Windatt CLA 2009-08-14 11:59:58 EDT
This bug would be a lot of work and very risky to fix, so this report is intended more as a readme.

In PDE we combine plug-ins from the workspace and the target into the plug-in registry.  The registry is used for many things including populating selection dialogs in the plug-in editor (adding import packages, required bundles, etc.).

If there is a bundle with the same symbolic name in the workspace and the target, we ignore the target bundle.  This makes sense the vast majority of the time, and is part of what makes PDE so flexible (as things are added to the workspace and modified the registry, classpath and target runtime get updated).

In some cases, however, a user may want to have both the version in the workspace and the one from their target.

For example, Mike encountered the following case:

1) Ant 1.6.5 in the target (default target platform)
2) Ant 1.7.0 in the workspace
3) Plug-in in the workspace requiring Ant 1.6.5

The only way to work around the problem was to have both Ant 1.6.5 and Ant 1.7.0 in the workspace.
Comment 1 Michael Rennie CLA 2009-08-14 12:09:27 EDT
Update to my example

In the workspace:
1. org.apache.ant (1.6.5) re-exported by project a.b.c
2. org.apache.ant (1.7.0) re-exported by project x.y.z

In target:
1. org.apache.ant (1.7.1)

Problem was that only 1.6.5 and 1.7.0 appeared in my target workspace.
Comment 2 Eclipse Webmaster CLA 2019-09-06 15:31:11 EDT
This bug hasn't had any activity in quite some time. Maybe the problem got resolved, was a duplicate of something else, or became less pressing for some reason - or maybe it's still relevant but just hasn't been looked at yet.

If you have further information on the current state of the bug, please add it. The information can be, for example, that the problem still occurs, that you still want the feature, that more information is needed, or that the bug is (for whatever reason) no longer relevant.
Comment 3 Julian Honnen CLA 2019-09-09 02:28:23 EDT
Please remove the stalebug flag, if this issue is still relevant and can be reproduced on the latest release.