| Summary: | Version are not canonicalized when loading from update site | ||||||
|---|---|---|---|---|---|---|---|
| Product: | [Eclipse Project] Equinox | Reporter: | Tom Hofmann <eclipse> | ||||
| Component: | p2 | Assignee: | P2 Inbox <equinox.p2-inbox> | ||||
| Status: | RESOLVED FIXED | QA Contact: | |||||
| Severity: | major | ||||||
| Priority: | P3 | CC: | pascal, simon_kaegi | ||||
| Version: | 3.4 | ||||||
| Target Milestone: | 3.5 M1 | ||||||
| Hardware: | PC | ||||||
| OS: | Windows XP | ||||||
| Whiteboard: | |||||||
| Attachments: |
|
||||||
Created attachment 107505 [details]
Test case
I have released a fix to this. that was fast! thanks, tom Note this fix caused a required capability with an empty range ("0.0.0") to be converted to range [0.0.0,1.0.0), which is incorrect. Bug 243422 is tracking that problem.
|
Classic update sites (without p2 metadata) working perfectly with Eclipse 3.3 don't work any longer if the following is true: A feature.xml lists a plug-in that only exists in a different version, e.g. <plugin id="org.apache.fop" version="0.94"/> but the file is "plugins/org.apache.fop_0.94.0.jar" (note the trailing .0) In Eclipse 3.3, the plug-in is nevertheless resolved and installed without problems. In 3.4, the update fails, leaving me with a partial install of some dependencies (Invalid zip file problem, see bug 228732). Major for me as this is a regression.