| Summary: | [regression] NPE running Ant task | ||||||
|---|---|---|---|---|---|---|---|
| Product: | [Eclipse Project] PDE | Reporter: | Michael Rennie <Michael_Rennie> | ||||
| Component: | API Tools | Assignee: | Curtis Windatt <curtis.windatt.public> | ||||
| Status: | VERIFIED FIXED | QA Contact: | |||||
| Severity: | major | ||||||
| Priority: | P3 | CC: | darin.eclipse | ||||
| Version: | 3.6 | ||||||
| Target Milestone: | 3.7 M3 | ||||||
| Hardware: | All | ||||||
| OS: | All | ||||||
| Whiteboard: | |||||||
| Attachments: |
|
||||||
|
Description
Michael Rennie
It would make sense that if there is no bundle context (it hasn't been started) the method should fall back to its old behavior. Created attachment 181307 [details]
Possible Fix
If we don't have a bundle context, can we still call code from PDE at all? If so, this patch will fix the problem by using PDE code directly rather than accessing it through the service (if there is no bundle context available).
If we cannot call any code from PDE, then we'll have to put back in the original code that scanned a directory. However, this will cause behaviour to differ significantly between having/not having a context.
Applied/Fixed. verified |