Community
Participate
Working Groups
When clicking "Add" in the "Required Plug-ins" column of the MANIFEST editor, the selected bundle is added with a bundle-version automatically set to the 3-first segments of the version available in target platform. However, the 3rd segment does not represent an API change, according to http://wiki.eclipse.org/index.php/Version_Numbering . That means that if a plugin has a bundle version set to x.y.z, it should also work with any x.y.*. It happens that the target platform for development is not the same as the target platform for release (for example, I use Eclipse SDK 3.5.2 on dev, and our product is built on top of Eclipse Platform 3.5.1). In that case, PDE UI automatically links me to bundles in version 3.5.2 and I have to change this everytime. If it were 3.5 by default, that would avoid this necessary extra-step, and avoid seeing build crashing when I forget to change the bundle-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.
Please remove the stalebug flag, if this issue is still relevant and can be reproduced on the latest release.
(In reply to Mickael Istria from comment #0) > However, the 3rd segment does not represent an API change, according to > http://wiki.eclipse.org/index.php/Version_Numbering . That means that if a > plugin has a bundle version set to x.y.z, it should also work with any x.y.*. Even though the API didn't change, the given version may contain bugfixes that triggered only a service segment increment. We should not blindly allow older versions IMO, that should be an explicit choice by the developer.
I'm partially agreeing with you, and don't really care enough about this feature to keep debating. It's not annoying me often (and actually I use the feature very rarely and it's often good enoug). So that's enough to make it a won't fix.
