There are abbrvs that combine final and private.

BUT private methods are automaticly final too!
No explicit marking them as final is needed.

I think that the same note applies on static.

[Mila] Here`s the list of the java abbrevs containing final:
    javaAbbrevMap.put("psf", "private static final ");
    javaAbbrevMap.put("psfi", "private static final int ");
    javaAbbrevMap.put("psfs", "private static final String ");
    javaAbbrevMap.put("psfb", "private static final boolean ");
    javaAbbrevMap.put("Psf", "public static final ");
    javaAbbrevMap.put("Psfi", "public static final int ");
    javaAbbrevMap.put("Psfs", "public static final String ");
    javaAbbrevMap.put("Psfb", "public static final boolean ");
The "private static final" has sense for the constants because making them only "private static" wouldn`t allow the compiler to substitute a constant in the resulting class as the value of the variabl
e could change during the class lifetime and they would be in fact changeable which is not desired for the constants.