Is there any complications or side effects for changing final field access/visibility modifier from private to protected?
<p>I have a <code>private final field</code> in one class and then I want to address that field in a subclass. I want to change field access/visibility modifier from <code>private</code> to <code>protected</code>, so I don't have to call <code>getField()</code> method from subclass and I can instead address that field directly (which is more clear and cohessive). Will there be any side effects or complications if I change <code>private</code> to <code>protected</code> for a <code>final</code> field?</p>

<p>UPDATE: from logical point of view, it's obvious that descendant should be able to directly access all predecessor fields, right? But there are certain constraints that are imposed on <code>private final</code> fields by JVM, like 100% initialization guarantee after construction phase(useful for concurrency) and so on. So I would like to know, by changing from <code>private</code> to <code>protected</code>, won't that or any other constraints be compromised?</p>
