Community
Participate
Working Groups
Is it possible to set the default value of the following settings to "ignore" (as it was in RC1)? "Local variable declaration hides another field or variable" "Field declaration hides another field or variable"
Usecase is for some code generation tools which are using these patterns a lot (knowing what they do). +1 for RC3. Erich - can you cast your vote ?
Motivation is that we changed the setting default late in the game, and some clients cannot adopt it. Thus request to revert.
Partial rollback from bug 76530 is trivial: Index: CompilerOptions.java =================================================================== RCS file: /home/eclipse/org.eclipse.jdt.core/compiler/org/eclipse/jdt/internal/compiler/impl/CompilerOptions.java,v retrieving revision 1.139 diff -u -r1.139 CompilerOptions.java --- CompilerOptions.java 9 Jun 2005 00:36:29 -0000 1.139 +++ CompilerOptions.java 16 Jun 2005 13:59:24 -0000 @@ -208,8 +208,6 @@ | UnhandledWarningToken | UnusedLocalVariable | UnusedPrivateMember - | FieldHiding - | LocalVariableHiding /*| NullReference*/; // Debug attributes
I am a bit concerned about our test suites. Dirk, comments ?
I will run them here with the patch.
I ran the tests that failed the last time and they still pass. We adpated the test to set their expected compiler options to make the independent of changes. I will run the refactoring tests as well to be 100% sure. But this will last another hour
Given that this was a last minute change +1 (I still think the new defaults are goodness for our developers)
Fixed and released in HEAD.
Verified using build N20050616-0010 + JDT Core HEAD.