| Summary: | [api tooling] API Baseline does not pick up stuff from dropins/ | ||||||
|---|---|---|---|---|---|---|---|
| Product: | [Eclipse Project] PDE | Reporter: | Martin Oberhuber <mober.at+eclipse> | ||||
| Component: | API Tools | Assignee: | PDE API Tools Inbox <pde-apitools-inbox> | ||||
| Status: | VERIFIED FIXED | QA Contact: | |||||
| Severity: | normal | ||||||
| Priority: | P3 | CC: | darin.eclipse, Michael_Rennie | ||||
| Version: | 3.4 | Flags: | Michael_Rennie:
review+
|
||||
| Target Milestone: | 3.5 M6 | ||||||
| Hardware: | PC | ||||||
| OS: | Windows XP | ||||||
| Whiteboard: | |||||||
| Attachments: |
|
||||||
|
Description
Martin Oberhuber
The baseline should be discovered using p2/runtime reflection to determine what bunldes are part of an install/configuration. PDE will migrate to use similar technology when discovering a target platform, and API tooling should follow. Marking as M5 candidate. Yeah - this will be pushed to M6 and will work of the new PDE target support that is going into M5. Created attachment 126479 [details]
patch
This fix uses PDE's new target definition model to retrieve installed bundles from the specified baseline location. If the location is not an installation, directory scanning proceeds as before.
We have had some discussion on the topic of baseline definition. Really, a baseline is just a target and could be composed the same way as a target definition (i.e. see new target platform preference page). For API analysis, the target is used for comparison rather than compilation. This patch just changes the way the initial set of bundles is fed into a baseline. Moving forward we should consider combining the target plaform and API baseline preference pages into one. Generally, when someonne defines a target platform for building, they should also define an API baseline. They could be managed in the same place. We could allow a baseline to be defined by a target definition file, similar to target platforms. Released fix to HEAD. Please verify, Mike. verified |