Summary: | Update Configurator reconciles platform.xml with newer features even when the site is marked not updateable. | ||||||
---|---|---|---|---|---|---|---|
Product: | [Eclipse Project] Platform | Reporter: | Nalini Ganapati <nalinig> | ||||
Component: | Update (deprecated - use Eclipse>Equinox>p2) | Assignee: | Platform-Update-Inbox <platform-update-inbox> | ||||
Status: | RESOLVED FIXED | QA Contact: | |||||
Severity: | critical | ||||||
Priority: | P2 | CC: | dejan | ||||
Version: | 3.3 | Keywords: | contributed | ||||
Target Milestone: | 3.3 RC4 | Flags: | dj.houghton:
review+
john.arthorne: review+ john.arthorne: review+ |
||||
Hardware: | PC | ||||||
OS: | All | ||||||
Whiteboard: | |||||||
Attachments: |
|
Description
Nalini Ganapati
2007-06-04 11:29:30 EDT
Created attachment 69970 [details]
Patch to not reconcile/update when a site has updateable set to false.
JUnit tests for Update are in org.eclipse.update.core.tests. A candidate for RC4 A well encapsulated patch for a concrete scenario: the code modification only comes into effect if the install location is not updatable. In other words, it does not affect out of the box Eclipse case. *** Bug 170000 has been marked as a duplicate of this bug. *** Just to clarify, is this just a case of a fix that was released for 3.2.2, but never put in HEAD for 3.3? Yes, although Nalini recognized that we need to cover another spot with the same 'isUpdatable' check. Otherwise it is the same fix. Ok, looks simple and safe. +1 for RC4 Released. |