Community
Participate
Working Groups
When I add a new dependency, I get something like: com.company.foo;bundle-version="1.2.0" Which eventually becomes incorrect when 1.3.0 is actually being used for development and nobody updates the min-version. Or, it becomes annoying when the bundle is updated to 2.0.0, causing a false negative when compiling against the newer version of the dependency. Please provide a preference setting so that only the following is added when using the "Add..." action in the "Required Plug-ins" section of the manifest editor and related UI pieces (like quick-fix, etc.): com.company.foo
As part of Bug #288396 we are investigating the right lower and upper version limits. I am updating the description of that one to bring this also under its scanner and closing this as duplicate. *** This bug has been marked as a duplicate of bug 288396 ***
IMO bug 288396 should not be fixed. Just because a major version of a bundle **might** break bundles which depend on it doesn't mean that it will. If you add an upper limit of ",4.0)", you are guaranteeing breakage. Why was this a dupe? 288396 is asking for more, this bug is asking for less (and implies a new preference page setting).
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. -- The automated Eclipse Genie.
This bug is marked as stale for some time. If it is still relevant for the current release, please reopen and remove the stalebug whiteboard tag.
