Some Eclipse Foundation services are deprecated, or will be soon. Please ensure you've read this important communication.

Bug 330926

Summary:	Preference needed to stop setting minimum version when adding bundle dependency
Product:	[Eclipse Project] PDE	Reporter:	Randy Hudson <hudsonr>
Component:	UI	Assignee:	PDE-UI-Inbox <pde-ui-inbox>
Status:	RESOLVED WONTFIX	QA Contact:
Severity:	normal
Priority:	P3	CC:	ankur_sharma
Version:	3.6
Target Milestone:	---
Hardware:	PC
OS:	Mac OS X - Carbon (unsup.)
Whiteboard:	stalebug
Bug Depends on:	288396
Bug Blocks:

Description Randy Hudson

2010-11-23 10:02:48 EST

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

Comment 1 Ankur Sharma

2010-11-24 00:07:49 EST

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 ***

Comment 2 Randy Hudson

2010-11-24 12:45:01 EST

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).

Comment 3 Eclipse Genie

2019-04-25 16:04:41 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.

--
The automated Eclipse Genie.

Comment 4 Lars Vogel

2019-10-29 05:33:01 EDT

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.