| Summary: | One corrupted bundle can cause the root site to disappear | ||||||
|---|---|---|---|---|---|---|---|
| Product: | [Eclipse Project] Platform | Reporter: | Thomas Watson <tjwatson> | ||||
| Component: | Update (deprecated - use Eclipse>Equinox>p2) | Assignee: | Platform-Update-Inbox <platform-update-inbox> | ||||
| Status: | RESOLVED WONTFIX | QA Contact: | |||||
| Severity: | normal | ||||||
| Priority: | P3 | CC: | eclipse, kim.moir, mike.haller | ||||
| Version: | 3.2 | Flags: | dejan:
review?
(dj.houghton) dejan: review? (tjwatson) |
||||
| Target Milestone: | --- | ||||||
| Hardware: | PC | ||||||
| OS: | Windows XP | ||||||
| Whiteboard: | obsolete | ||||||
| Attachments: |
|
||||||
|
Description
Thomas Watson
I am attaching a patch that is rethrowing the exception: Created attachment 68794 [details]
The patch to rethrow the original exception instead of eating it
I was able to reproduce the original problem when I deleted the exloded project for the corruped bundle and replaced it with the signed jar. The attached patch will cause error dialogs to show up. The message isn't ideal because it does not tell you which JAR is causing it, but is definitely a step forward. When I apply the patch and put the patched version of the bundle into the i0525 build, I get an error dialog 3 times on my way to the "install new features" screen. The message is: "invalid SHA1 signature file digest for about.html" which should be capitalized and have proper punctuation at the end. Unfortunately without the name of the bundle that is causing the problem, this isn't much help. How much work is it to add the name of the bundle? The result of this also means that the site is disabled and we get into the same state as mentioned in bug 189000. Does it make sense to enable the site depending on what type of error we are getting? Tom mentions that perhaps catching the security exception in JarEntryContentReference#getInputStream and maybe rethrow an IOException with more information and use SecurityException as the cause, might be better. Thoughts? Yes, I was thinking about it on the way to lunch :-). The SHA message is coming from the exception - I didn't create it. Since this is not a regression relative to 3.2, we will not address it in 3.3. The Eclipse Update component is no longer under development, and no longer exists in the Eclipse Platform 4.x stream. If this problem still occurs in Eclipse Platform 4.2 or later, please enter a new bug report against Equinox p2. |