This Bugzilla instance is deprecated, and most Eclipse projects now use GitHub or Eclipse GitLab. Please see the deprecation plan for details.
Bug 247951 - Ordering of Collections Returned from APIs
Summary: Ordering of Collections Returned from APIs
Status: CLOSED WONTFIX
Alias: None
Product: Tigerstripe (Archived)
Classification: Technology
Component: Core (show other bugs)
Version: 0.4   Edit
Hardware: PC Windows XP
: P3 normal (vote)
Target Milestone: 0.4M0   Edit
Assignee: Project Inbox CLA
QA Contact:
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2008-09-19 07:21 EDT by John Worrell CLA
Modified: 2012-03-01 16:28 EST (History)
2 users (show)

See Also:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description John Worrell CLA 2008-09-19 07:21:46 EDT
It would be enormously useful if the ordering of the Collections returned from various parts of the TS API were predictable and well-determined. By way of example, if I invoke the method getContainedModelComponents() on the same artifact in the same TS project, I should be certain that the artifacts will appear in the same order in each case.

The key motivation for this is in regression testing where the if the order of the artifacts can be guaranteed to be the same, a simple compare of 2 sets of gerated files can very quickly give a result, wheras if the ordering is not the same a more complex eye-ball diff is usually necessary.
Comment 1 Eric Dillon CLA 2008-09-19 13:03:51 EDT
Very valid point.

I believe the main reason because the order is inconsistent is the way we add/replace artifacts in the manager (and caches) each time an artifact is changed.

Comment 2 Navid Mehregani CLA 2012-03-01 16:28:23 EST
I don't want to change the implementation of any of these APIs.  If there is still a need for this, please reopen.  

Callers can simply do a search to compare two separate collections.