| Summary: | <archive> tags don't work when updating | ||
|---|---|---|---|
| Product: | [Eclipse Project] Platform | Reporter: | Pratik Shah <ppshah> |
| Component: | Update (deprecated - use Eclipse>Equinox>p2) | Assignee: | Platform-Update-Inbox <platform-update-inbox> |
| Status: | RESOLVED INVALID | QA Contact: | |
| Severity: | major | ||
| Priority: | P3 | ||
| Version: | 3.1 | ||
| Target Milestone: | --- | ||
| Hardware: | PC | ||
| OS: | All | ||
| Whiteboard: | |||
Invalid. Change the valid update preference from the default of equivalent to compatible fixed this. |
Create a local update site as follows: updates (dir) |-> site.xml |-> 3.0 (dir) |-> features (dir) |-> <feature-jars> |-> plugins (dir) |-> <update-jars> The site.xml would look something like this: <feature url="3.0/features/<feature-name>_3.1.0.jar" patch="false" id="<feature-name>" version="3.1.0"> <category name="3.1" /> </feature> <archive path="plugins/<plugin-name>_3.1.0.jar" url="3.0/plugins/<plugin- name>_3.1.0.jar" /> This setup works just fine during discovery (search for new features to be installed). However, when updating (when you have an older version of that feature installed already), no updates are found. I tested this locally by changing the update url in the feature.xml to "file:/D:/updates". Marking this bug as major and not critical because, obviously, the workaround is to copy the files to updateURL/features and updateURL/plugins directory.