Bugzilla – Full Text Bug Listing
| Summary: | Rollback of a 342 based product to a 341 and then subsequently to 340 results in an unlaunchable configuration. | ||||||||
|---|---|---|---|---|---|---|---|---|---|
| Product: | [Eclipse Project] Equinox | Reporter: | Nalini Ganapati <nalinig> | ||||||
| Component: | p2 | Assignee: | Pascal Rapicault <pascal> | ||||||
| Status: | RESOLVED NOT_ECLIPSE | QA Contact: | |||||||
| Severity: | normal | ||||||||
| Priority: | P3 | CC: | dj.houghton, pascal | ||||||
| Version: | 3.4.2 | ||||||||
| Target Milestone: | --- | ||||||||
| Hardware: | All | ||||||||
| OS: | All | ||||||||
| Whiteboard: | |||||||||
| Attachments: |
|
||||||||
Created attachment 128140 [details]
The failing 340->341->342->341->340 rollback scenario.
The zip contains the configuration, eclipse.ini, config.ini, platform.xml, bundles.info and the last p2 profile for this failing scenario.
*** Bug 266198 has been marked as a duplicate of this bug. *** The problem was occurring because the profile in which the operation was being executed was installing features (org.eclipse.update.install.features=true) and the launcher plug-in was no longer there. It was not happening in a 3.4.0 based configuration because the features were not being installed and the mismatch of the launcher plug-in was not an issue. |
Created attachment 128139 [details] The successful 340->341->340 rollback scenario Build ID: Eclipse 3.4.0, 3.4.1 ad 3.4.2 When a 340 based product(e.g. RAD 750) is updated to 341(RAD 751), updated to 342(RAD 752) and then rolled back to 341 and then subsequently to 340, this results in an unlaunchable configuration. Note that the following rollback scenarios are successful - 340 -> 341 -> 340 340 -> 342 -> 340 340 -> 341 -> 342 -> 341 What is not successful is only this scenario - 340 -> 341 -> 342 -> 341 -> 340.