> E.g. the AbstractTree has protected mutable fields (bad practice per se, if > exported even worse) If that is by design (required for MutableTree) would it still be bad. What would be the issue?
> Or TreeConstants exposing an „internal“ constant (should be a final class not > an interface, actually) Can change it to class but I do not see much issue in using interface as holder for constants. Allows me to save bit on redundant typing of 'public static final'!. The constant is not that internal, just a name of hidden field Rest all classes are marked final so should be ok. Chetan Mehrotra
