Bugzilla – Full Text Bug Listing
| Summary: | Sort include path entries | ||||||
|---|---|---|---|---|---|---|---|
| Product: | [WebTools] JSDT | Reporter: | Michael Rennie <Michael_Rennie> | ||||
| Component: | General | Assignee: | Project Inbox <jsdt.javascript-inbox> | ||||
| Status: | RESOLVED WONTFIX | QA Contact: | Nitin Dahyabhai <thatnitind> | ||||
| Severity: | enhancement | ||||||
| Priority: | P3 | ||||||
| Version: | 3.2 | ||||||
| Target Milestone: | --- | ||||||
| Hardware: | PC | ||||||
| OS: | Linux | ||||||
| Whiteboard: | |||||||
| Attachments: |
|
||||||
The tabs already separate the Include Path entries into their own kinds, but the actual ordering is intentionally not sorted. In JDT, the Build Path's ordering is used to determine the runtime classpath ordering. As we work through how to properly insert files into Rhino for debugging, the order will have importance to us as well. |
Created attachment 178414 [details] screen shot build id: 20100813105432 Steps: 1. on the Include Path properties page for a JS project add a variety of entries and notice that there is no sorting at all. See the attached screenshot for an example. The entries should be grouped by kind and sorted lexicographically within their grouping.