I have an abstract class that has such a method:

 protected abstract String doStuff( String request );

It's protected because I want users of my code to access it via the superclass.
In my subclass, to match, I have:

 protected final String doStuff( String request ) { // [...] }

When I run Tools->Synchronize on that subclass, the Confirm Changes dialog says:

 Update Method protected final java.lang.String doStuff(String) to protected
abstract java.lang.String doStuff(String).

That kindof makes sense.. so when I process that, this is the change it makes in
my subclass:

 protected final String doStuff( String request ) { // [...] }
to
 public final String doStuff( String request ) { // [...] }

Why would it change the visibility to public after it says it needs to satisfy
it as protected - especially after it says it needs to be protected? I think it
should use the same visibility as the abstract class defines. I definetly feel
it shouldn't change method visibility that already satisfies the abstract
method. This isn't an Interface, not everything needs to be public.