| Summary: | Remove the use of the 'deltas' approach | ||
|---|---|---|---|
| Product: | [Eclipse Project] Platform | Reporter: | Eric Moffatt <emoffatt> |
| Component: | UI | Assignee: | Platform UI Triaged <platform-ui-triaged> |
| Status: | RESOLVED FIXED | QA Contact: | |
| Severity: | normal | ||
| Priority: | P3 | CC: | ob1.eclipse, remy.suen, tom.schindl |
| Version: | 4.1 | ||
| Target Milestone: | --- | ||
| Hardware: | PC | ||
| OS: | Windows XP | ||
| Whiteboard: | |||
|
Description
Eric Moffatt
The 99% case is true for deployment but not for development time, where one adds/removes/moves stuff around We also need to check that the final approach works OK for dynamic bundle addition/removal. M2 is done... Moving to M4; once we get trim dragging done it'll be more apparent why this makes sense...we may defer this to 4.3. I'll move this to M7 (just so I can move it to 4.3 once the slot shows up), it's essentially off the plate for 4.2 since it's not causing issues.... The main issue is that we need to come up with some mechanism to prevent contributions from being added multiple times... Already Done... |