Bug 213020 - [api tooling] compute minimal required bundle versions
Summary: [api tooling] compute minimal required bundle versions
Status: ASSIGNED
Alias: None
Product: PDE
Classification: Eclipse Project
Component: API Tools (show other bugs)
Version: 3.4   Edit
Hardware: All All
: P3 enhancement (vote)
Target Milestone: ---   Edit
Assignee: PDE API Tools Inbox CLA
QA Contact:
URL:
Whiteboard:
Keywords:
: 218664 222123 365397 (view as bug list)
Depends on:
Blocks:
 
Reported: 2007-12-14 09:43 EST by Darin Wright CLA
Modified: 2015-01-11 07:30 EST (History)
6 users (show)

See Also:

Attachments
Work in progress (30.79 KB, patch)
2008-02-28 23:56 EST, Darin Wright CLA 		no flags Details | Diff
updated patch (36.85 KB, patch)
2008-02-29 11:02 EST, Darin Wright CLA 		no flags Details | Diff
updated patch (4.25 KB, patch)
2008-02-29 15:31 EST, Darin Wright CLA 		no flags Details | Diff
zip of code that does prepreq version analysis (9.68 KB, application/octet-stream)
2008-04-28 12:58 EDT, Darin Wright CLA 		no flags Details
Show Obsolete (1) View All Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.
Description Darin Wright CLA 2007-12-14 09:43:14 EST 
Often as developers create the next version of a bundle/plug-in in a release, they just update the minimum required version of required bunldes. For example, the debug plug-ins that require org.eclipse.core.resources claim to require the version of o.e.c.resources in 3.4 (but the debug plug-ins may still run properly with a previous version of o.e.c.resources, based on the API used).

The tendency to update required bundle versions is based on what we actually test at runtime (i.e. we know we run with the latest version of a required plug-in, and we don't test with earlier versions - as those configurations of plug-ins don't even exist).

API tooling should be able to determine the minimal version of a required bundle. For example, given a complete API profile we should be able to resolve all references from component A to component B, in that profile. Then, given several versions of compnonent B, we can determine which versions of component B satisfy all those references.
Comment 1 Darin Wright CLA 2008-01-08 09:20:02 EST 
Investigate for 3.4
Comment 2 Darin Wright CLA 2008-02-28 23:56:01 EST 
Created attachment 91101 [details]
Work in progress
Comment 3 Darin Wright CLA 2008-02-29 11:02:14 EST 
Created attachment 91203 [details]
updated patch
Comment 4 Darin Wright CLA 2008-02-29 15:31:09 EST 
Created attachment 91240 [details]
updated patch

Remaining patch adds support to PDE to contribute action to manifest editor. The wizard is in HEAD in API tools.
Comment 5 Darin Wright CLA 2008-03-10 17:56:32 EDT 
*** Bug 222123 has been marked as a duplicate of this bug. ***
Comment 6 Darin Wright CLA 2008-04-28 12:58:13 EDT 
Created attachment 97803 [details]
zip of code that does prepreq version analysis

Here's the code I removed from HEAD since we aren't using it in 3.4
Comment 7 Darin Wright CLA 2008-04-28 13:12:50 EDT 
Note, Also see the following versions for the following classes that had support code for analysis:

ApiUseAnalyzer: 1.31
ApiToolsLabelProvider: 1.8
Comment 8 Dani Megert CLA 2008-09-02 12:18:31 EDT 
It should not only flag that I could use lower version but report API problems if I used API that is not available in the indicated plug-in i.e. if I need to specifiy a higher version.
Comment 9 Darin Wright CLA 2008-09-02 12:24:50 EDT 
(In reply to comment #8)
> It should not only flag that I could use lower version but report API problems
> if I used API that is not available in the indicated plug-in i.e. if I need to
> specifiy a higher version.

Yes, there is a M3 plan item for this, but not sure we have a bug for it yet:

"Flag when new API is used in a required bunlde that requires the version range to be incremented/updated (i.e. using a new API, so lower bound needs updating)"
Comment 10 Darin Wright CLA 2009-03-20 10:28:20 EDT 
*** Bug 218664 has been marked as a duplicate of this bug. ***
Comment 11 Markus Keller CLA 2010-11-24 06:47:52 EST 
Looks similar to bug 255771.
Comment 12 Dani Megert CLA 2014-10-10 05:57:30 EDT 
*** Bug 365397 has been marked as a duplicate of this bug. ***