Community
Participate
Working Groups
Currently plug-ins located in the workspace are considered to be a superior to those located in the target platform. This is not always a desired behaviour, because there is no way of telling which plugins/packages will be actually available during runtime. A preference should be available which gives the user following choice () Prefer workspace plugins and packages () Process plugins in the same way during development as during runtime
(In reply to comment #0) > Currently plug-ins located in the workspace are considered to be a superior to > those located in the target platform. This is only the default behavior. > This is not always a desired behaviour, because there is no way of telling > which plugins/packages will be actually available during runtime. You may configure the launch configuration and make it pick specific plug-ins from the workspace or from the target. You can do this even at feature level using feature based launching. > A preference should be available which gives the user following choice > () Prefer workspace plugins and packages > () Process plugins in the same way during development as during runtime dev environment depends on the current target platform settings. One may wish to run the plug-ins in different runtime environments, hence multiple launch configurations can be used to run them with different runtime settings.
This is just a rewording of bug 339654. PDE gives preference to workspace plug-ins by default because it is assumed that you want to work with the plug-ins in your workspace. All bundle requirements should be enforced by version constraints. The PDE State is not expected to reflect the final State you will have in your product. PDE must combine bundles from both the workspace and target, some of which may have conflicting versions. It makes complete sense for the conflicts to be resolved by choosing workspace plug-ins first. Furthermore, changing this behaviour would likely break a very common scenario. 1) Have bundle foo 3.7.0.N20110317 in your target 2) To make a change, check out the bundle from CVS 3) Edit the code and launch If we always prefer the highest version, this would fail because the workspace version would be 3.7.0.qualifier (lower than the target version)
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. If the bug is still relevant please remove the stalebug whiteboard tag.
