Bugzilla – Full Text Bug Listing
| Summary: | [clean up] Stops working after 100 problems in one CU | ||
|---|---|---|---|
| Product: | [Eclipse Project] JDT | Reporter: | Markus Keller <markus.kell.r> |
| Component: | UI | Assignee: | Markus Keller <markus.kell.r> |
| Status: | VERIFIED FIXED | QA Contact: | |
| Severity: | normal | ||
| Priority: | P3 | CC: | daniel_megert |
| Version: | 3.7 | ||
| Target Milestone: | 3.7 M2 | ||
| Hardware: | All | ||
| OS: | All | ||
| Whiteboard: | |||
| Bug Depends on: | |||
| Bug Blocks: | 325195 | ||
Rajesh, can you please write a new test for this? Something like CleanUpTest#testAddOverride15(), but where you generate 200 methods in a loop. The test should fail in HEAD but become green with the fix in comment 0. > Possible fix is to add
>
> options.put(JavaCore.COMPILER_PB_MAX_PER_UNIT, "0"); //$NON-NLS-1$
>
> in RefactoringASTParser#getCompilerOptions(IJavaElement).
I've released that to HEAD for 3.7 M2.
(In reply to comment #1) > Rajesh, can you please write a new test for this? Something like > CleanUpTest#testAddOverride15(), but where you generate 200 methods in a loop. > The test should fail in HEAD but become green with the fix in comment 0. Filed bug 325195 for the test. Verified in I20100915-2024. |
HEAD Clean Ups like "Add missing Override annotations" stop working after 100 problems in one CU. Problem is most probably that the compiler only reports the first 100 problems. That makes sense in the Java editor and for batch compilations, but refactorings and clean ups should see all problems. Possible fix is to add options.put(JavaCore.COMPILER_PB_MAX_PER_UNIT, "0"); //$NON-NLS-1$ in RefactoringASTParser#getCompilerOptions(IJavaElement).