| Summary: | FUP of bug 363293: Fix the incorrect added resource close | ||||||||
|---|---|---|---|---|---|---|---|---|---|
| Product: | [Eclipse Project] JDT | Reporter: | Satyam Kandula <satyam.kandula> | ||||||
| Component: | Core | Assignee: | Stephan Herrmann <stephan.herrmann> | ||||||
| Status: | VERIFIED FIXED | QA Contact: | |||||||
| Severity: | minor | ||||||||
| Priority: | P3 | CC: | satyam.kandula, srikanth_sankaran, stephan.herrmann | ||||||
| Version: | 3.8 | ||||||||
| Target Milestone: | 3.8 M7 | ||||||||
| Hardware: | PC | ||||||||
| OS: | Windows 7 | ||||||||
| Whiteboard: | |||||||||
| Bug Depends on: | 362332, 368546 | ||||||||
| Bug Blocks: | |||||||||
| Attachments: |
|
||||||||
|
Description
Satyam Kandula
Created attachment 207972 [details]
Proposed patch
I'll use bug 362332 to change the reported warning into saying "potential leak". After that I'll apply the test change. I just checked whether 362332 indeed solved this issue, but unfortunately we'll have to wait for the fix from bug 368546, too. Relaxing target milestone from 3.8 M5 to 3.8. If you plan to include a fix for this in 3.8 M7, please adjust the target suitably, so it becomes easier to track. I assume this should be easy now, as both pre-reqs are resolved now. Created attachment 214450 [details]
slightly more explicit fix
OK, an unconditional close is no longer needed to silence the warning.
Satyam, do you want to review the patch (which basically does the same as what you already proposed) or is it OK to push without review since it's a tests-only patch?
(In reply to comment #6) Please go ahead and push it. Released for 3.8 M7 via commit ebee4ac330d3dc7dc9f8f11cab338cf905bf6dd5 Verified for 3.8M7 by looking at the code. |