Closed GoogleCodeExporter closed 8 years ago
Adding @Override annotations is a good thing to do as people come across places
where they're missing, but issues and patches are a way to high and overhead
mechanism for doing this.
A more efficient way is to just adjust our Eclipse settings appropriately so
that they get flagged as warnings. That way they'll improve over time (and
we'll keep them clean).
Having said that, I did this class and a bunch of others in surrounding
packages.
Original comment by tfmorris
on 6 Jun 2011 at 10:17
Original comment by tfmorris
on 18 Sep 2012 at 3:01
Original issue reported on code.google.com by
thadguidry
on 28 Jan 2011 at 10:15Attachments: