| Summary: | Error handling in ProjectSetImporter.importProjectSet is wrong | ||
|---|---|---|---|
| Product: | [Eclipse Project] Platform | Reporter: | Dani Megert <daniel_megert> |
| Component: | Team | Assignee: | Dani Megert <daniel_megert> |
| Status: | RESOLVED FIXED | QA Contact: | |
| Severity: | normal | ||
| Priority: | P3 | CC: | daniel_megert, tomasz.zarna |
| Version: | 3.8 | ||
| Target Milestone: | 3.8 M5 | ||
| Hardware: | All | ||
| OS: | All | ||
| Whiteboard: | |||
The biggest bug is that referenceStrings is not cleared when an exception happens. As a result, the next provider tries to load project references from the previous one and then fails badly. Fixed in master: 45e2a2fe42c326895aaa0a4323b9650225fa7863 |
3.8 M4. The error handling in ProjectSetImporter.importProjectSet needs to be improved: it collects the TeamExceptions but if some other exceptions happen (like an assertion failure) then the TeamExceptions are swallowed i.e. not reported. Also, CVSProjectSetCapability.addToWorkspace should probably covert the IAE into a TeamException. Test Case: 1. install 3.8 M4 plus EGit 2. start with new workspace 3. import team project set from attachment 208048 [details]