| Summary: | Source look-up should be generalized | ||||||
|---|---|---|---|---|---|---|---|
| Product: | [WebTools] JSDT | Reporter: | Michael Rennie <Michael_Rennie> | ||||
| Component: | Debug | Assignee: | Michael Rennie <Michael_Rennie> | ||||
| Status: | VERIFIED FIXED | QA Contact: | Simon Kaegi <simon_kaegi> | ||||
| Severity: | normal | ||||||
| Priority: | P3 | CC: | thatnitind | ||||
| Version: | 3.2 | ||||||
| Target Milestone: | 3.3 M2 | ||||||
| Hardware: | All | ||||||
| OS: | All | ||||||
| Whiteboard: | |||||||
| Attachments: |
|
||||||
applied to HEAD |
Created attachment 176697 [details] fix code from HEAD Our JavaScriptSourceLookupParticipant has logic in it that would be better in a utility class so that other consumers can look source up in the 'Extenal JavaScript Source' project and resolve URIs, etc for source elements. The patch provides a new utility class SourceLookup in org.eclipse.wst.jsdt.debug.internal.core.launching (can be made API if requested) with the following methods: - getSourceURI(obj) - getSource(obj) - getExternalSource(uri, obj)