Bug 300409 - [target] New proposed target API breaks API tools
Summary: [target] New proposed target API breaks API tools
Status: RESOLVED INVALID
Alias: None
Product: PDE
Classification: Eclipse Project
Component: UI (show other bugs)
Version: 3.6   Edit
Hardware: All All
: P3 normal (vote)
Target Milestone: ---   Edit
Assignee: Curtis Windatt CLA
QA Contact:
URL:
Whiteboard:
Keywords:
Depends on:
Blocks: 287619
  Show dependency tree
 
Reported: 2010-01-21 12:48 EST by Michael Rennie CLA
Modified: 2010-08-20 16:24 EDT (History)
2 users (show)

See Also:

Attachments
patch (8.13 KB, application/octet-stream)
2010-01-21 13:12 EST, Michael Rennie CLA 		no flags Details
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 Michael Rennie CLA 2010-01-21 12:48:03 EST 
I20100121-0800

Helping test the new API from the branch, I found a few places that the current state of the branch breaks API tools. In our baseline and API use code when building the bundle collection we use IResolvedBundle to get at the BundleInfo and to know if a bundle is a source bundle or not and to get the location information. 

In the API branch this type has been removed, and updating our code to use the "new world" i.e. ITargetDefinition.getProvisionedBundles(), does not allow us to know if any of the bundles are source bundles or not.

Affected API tools classes:

ApiBaselineWizardPage
ApiUseScanJob
Comment 1 Michael Rennie CLA 2010-01-21 13:12:07 EST 
Created attachment 156830 [details]
patch

This patch updates API tools to use the new branch code (for testing)
Comment 2 Curtis Windatt CLA 2010-08-20 16:24:33 EDT 
The code from the branch is not going to be committed.  If the api changes in the future, we can just create a new patch for API tooling.