| Summary: | Collector should handle duplicates | ||||||
|---|---|---|---|---|---|---|---|
| Product: | [Eclipse Project] Equinox | Reporter: | John Arthorne <john.arthorne> | ||||
| Component: | p2 | Assignee: | John Arthorne <john.arthorne> | ||||
| Status: | RESOLVED FIXED | QA Contact: | |||||
| Severity: | normal | ||||||
| Priority: | P3 | CC: | agcattle, susan | ||||
| Version: | 3.5 | ||||||
| Target Milestone: | 3.5 M4 | ||||||
| Hardware: | PC | ||||||
| OS: | Windows XP | ||||||
| Whiteboard: | |||||||
| Bug Depends on: | |||||||
| Bug Blocks: | 252456 | ||||||
| Attachments: |
|
||||||
|
Description
John Arthorne
I will investigate if there is any impact here. Some of the UI collectors filter out duplicates as a side effect of performing other work, such as finding the latest version of an IU. Bug #252456 discusses the need for the UI collectors to do this more generally, and I think it'd be great if Collector supported this. I don't know of a case in the UI that relies on duplicates being there. Great, I was going to ask you about this. From the core use of collectors, it looks like we typically do not check for duplicates, and I suspect this will either cause problems or result in us doing extra work if the same IU is present in multiple repositories. I'm leaning towards just making Collector handle duplicates without exposing an option to allow duplicates. (In reply to comment #3) >I'm leaning towards just making Collector > handle duplicates without exposing an option to allow duplicates. That sounds like the right approach, we can always open a bug later if the assumptions weren't true. Created attachment 117694 [details]
Fix
Released. |