Remove @Override annotration解决

y Michael Myers♦ Nov 19 '10 at 15:17

This question is protected to prevent "thanks!", "me too!", or spam answers by new users. To answer it, you must have earned more than 10 reputation on this site.

5 Answers

activeoldestvotes

up vote275down voteaccepted

Eclipse is defaulting to Java 1.5 and you have classes implementing interface methods (which in Java 1.6 can be annotated with @Override, but in Java 1.5 can only be applied to methods overriding a superclass method).

Go to your project/ide preferences and set the java compiler level to 1.6 and also make sure you select JRE 1.6 to execute your program from eclipse.

link|improve this answer

answered Nov 5 '09 at 3:33 alphazero 7,25211010

Thank you so much, never would have figured that out! – Tim H Nov 5 '09 at 4:02

Happy to help. Been bitten by the same myself ;) – alphazero Nov 5 '09 at 4:28

+1 for short and clear answer. – OemerA Oct 12 '10 at 8:38

Same issue here, thanks, great answer. – DavidG Dec 28 '10 at 15:54

2

My project was set to 1.6, so I shot for the stars and set it to 1.5, rebuilt, then back to 1.6. Miraculously this resolved my issue. Thanks for pointing me in the right direction! – Michael Krauklis Feb 9 '11 at 20:43

show 6 more comments

feedback

up vote65down vote

With Eclipse Galileo you go to Eclipse -> Preferences menu item, then select Java and Compiler in the dialog.

Now it still may show compiler compliance level at 1.6, yet you still see this problem. So now select the link "Configure Project Specific Settings..." and in there you'll see the project is set to 1.5, now change this to 1.6. You'll need to do this for all affected projects.

This byzantine menu / dialog interface is typical of Eclipse's poor UI design.

link|improve this answer

answered Sep 8 '10 at 3:48 Paul 1,442411

+1 - this was driving me crazy. – I82Much Sep 8 '10 at 17:10

+1 Good followup. I wish the answers were consolidated. – Justin Nov 18 '10 at 12:43

3

+! excellent supplement to the above answer – Anand Jan 21 '11 at 10:54

Great stuff! Thanks – m6tt Nov 19 '11 at 23:42

feedback

up vote5down vote

In case this happens to anyone else who tried both alphazero and Paul's method and still didn't work.

For me, eclipse somehow 'cached' the compile errors even after doing a Project > Clean...

I had to uncheck Project > Build Automatically, do a clean and build again.

link|improve this answer

answered Jan 26 '11 at 17:22 Rollin_s 31337