| Summary: | Control the ordering of the root files | ||||||
|---|---|---|---|---|---|---|---|
| Product: | [Eclipse Project] PDE | Reporter: | Pascal Rapicault <pascal> | ||||
| Component: | Build | Assignee: | pde-build-inbox <pde-build-inbox> | ||||
| Status: | RESOLVED FIXED | QA Contact: | |||||
| Severity: | normal | ||||||
| Priority: | P3 | CC: | jeffmcaffer, n.a.edgar | ||||
| Version: | 3.1 | ||||||
| Target Milestone: | 3.1 RC2 | ||||||
| Hardware: | PC | ||||||
| OS: | Windows 2000 | ||||||
| Whiteboard: | |||||||
| Bug Depends on: | |||||||
| Bug Blocks: | 97469 | ||||||
| Attachments: |
|
||||||
|
Description
Pascal Rapicault
One scenario is having the SDK feature override the config.ini from the platform feature, in order to refer to an SDK product extension with different preference overrides for the initial perspective, and perhaps branding differences. Created attachment 22038 [details]
Patch to AssemblyInformation
DJ could you review? We are switching from using a Set to a LinkedList. I see the early return in #addRootFileProvider. Are there any other places where we might be adding files to the list? Is it safer to do a #contains check first to ensure the resource doesn't already exist? What are the consequences if the file is added to the list twice? I don't have a clear memory as to why I don't use contains() in all this part of the code, but at the time I had some good reasons that I can't remember now. So I suggest that for now we keep the fix simple, and that we review the usage of contains() post 3.1. What do you think? I think that adding #contains is the simple fix because it ensures the entries aren't in the list twice and we can review taking it out for 3.2. :-) Fixed in HEAD with the contains(). |