Community
Participate
Working Groups
I20050218-1600 NamingConventions.suggestFieldNames(..) does not consider the 'final' modifier for constants. E.g. when asked: NamingConventions.suggestFieldNames( project, "", "ArrayList", 0, Flags.AccStatic | Flags.AccFinal, new String[0]); ..., the answer is {"list", "arrayList"}. Expected: {"LIST", "ARRAY_LIST"}
If we want the full flexibility here, then you should introduce new prefix/suffix options for constants (static final fields). But IMO, it would be sufficient to just use no prefix/suffix at all for constants.
Deferred post 3.2
Could this bug please be considered for 3.3? It would be quite hard for us to work around this -- we would basically have to duplicate most of org.eclipse.jdt.internal.core.InternalNamingConventions.suggestNames(..).
considering for 3.4
Time permitting for 3.4
Deferring post 3.4
Targeting M3
Released for 3.5M3. This bug is fixed by the fix for bug 38111
Verified for 3.5M3 using I20081026-2000