| Summary: | Update Manager throws ArithmeticException | ||||||
|---|---|---|---|---|---|---|---|
| Product: | [Eclipse Project] Platform | Reporter: | David Hergert <david.hergert> | ||||
| Component: | Update (deprecated - use Eclipse>Equinox>p2) | Assignee: | Platform-Update-Inbox <platform-update-inbox> | ||||
| Status: | RESOLVED FIXED | QA Contact: | |||||
| Severity: | normal | ||||||
| Priority: | P3 | CC: | caniszczyk, cbeth, dejan, pforeman, psingh, raji, romain.castell, zzhang | ||||
| Version: | 3.3 | ||||||
| Target Milestone: | 3.5 M6 | ||||||
| Hardware: | PC | ||||||
| OS: | Windows XP | ||||||
| Whiteboard: | |||||||
| Attachments: |
|
||||||
|
Description
David Hergert
Created attachment 71954 [details]
Patch for UpdateSearchRequest
I just ran into this same problem and have a fix for it. When a feature is missing an update site, a monitor gets created with 0 tasks to execute. This patch will make sure that we return from the search without doing anything. I have attached above as "Patch for UpdateSearchRequest" There was only one line changed but it looks like a lot of lines changed because I indented everything after if (ntasks > 0). (In reply to comment #2) Thanks for the patch, Paul. I'd like to try it out. But forgive my novice question, is there a document or website somewhere explaining how to patch Eclipse itself and then run it with the patched code? Also, the target milestone for this bug is not set. Will your fix be targeted for 3.4? David, You can grab the source here: http://wiki.eclipse.org/index.php/CVS_Howto Once you have CVS set up in eclipse you can 1. Select the org.eclipse.update.core project in the Navigator or other view. 2. Context Menu->Compare With->Patch... 3. Fill in the location of the patch file 4. Click Next. A summary of changed files will appear. 5. Click Finish. The changes are now merged into the workspace. Once this is done you can then build your own jar that includes this patch. At this point the patch has to be reviewed and accepted by the Eclipse team. They will decide what target will be set for the patch. Good luck! Dejan, this is a good candidate for 3.3.1, I'll mark it so. Didn't get in. (In reply to comment #6) Will this be in 3.4? Can someone confirm that this is fixed for 3.3.2 or 3.4? The activity on this issue has gone silent. This wasn't fixed in 3.3.2 or 3.4. *** Bug 263078 has been marked as a duplicate of this bug. *** Released a fix to HEAD. |