@Override Error in Eclipse: How to Defeat "Must Override a Superclass Method"

Introduction: Why is Eclipse Yelling at You?

You imported a foreign project into Eclipse, clicked Build, and suddenly — dozens of red crosses. The error: "Must Override a Superclass Method". Sound familiar? If you are learning to program in Java or working with someone else's code, this situation is a real bummer. Especially when the project built perfectly in another IDE or via Maven.

On Stack Overflow, this question has garnered thousands of views. And for good reason: the problem is insidious. Eclipse is a powerful environment, but its compiler settings can play a nasty trick. In this article, we will break down where the "Must Override a Superclass Method" error comes from, and most importantly — how to fix it once and for all.

We will look at three main causes and provide step-by-step instructions with real code examples. You will learn how to configure Eclipse so it doesn't complain about correct code, and how to avoid this problem in the future.

What Does the "Must Override a Superclass Method" Error Mean?

The error occurs when you use the @Override annotation before a method that, according to Eclipse, does not override a method from a parent class or interface. In reality, the problem is most often not in your code, but in the Java compiler settings in Eclipse.

The @Override annotation was introduced in Java 5 (1.5) for methods overriding superclass methods. But in Java 6, it was allowed to be used for methods implementing interfaces as well. If your project is set to Java 5, but you are writing code for Java 8 — Eclipse will complain.

Here is a typical example that causes the error:

public interface Animal {\n    void makeSound();\n}\n\npublic class Dog implements Animal {\n    @Override\n    public void makeSound() {\n        System.out.println("Woof!");\n    }\n}\n

If the project's compliance level is Java 5, Eclipse will say: "Must Override a Superclass Method". Even though the code is perfectly correct for Java 6 and above.

Cause 1: Incorrect Compiler Compliance Level

This is the most common cause. Eclipse has a setting called Compiler compliance level, which determines which version of Java it expects. If you import a project created in another IDE, this setting often gets reset to an outdated version.

How to Fix:

\n
1. Right-click on the project → Properties.
\n
2. Go to Java Compiler.
\n
3. Uncheck "Use compliance from execution environment".
\n
4. Select a Compiler compliance level — for example, 1.8 or 11 (depending on your project).
\n
5. Click Apply and Close.
\n
6. Rebuild the project: Project → Clean.
\n

Important: If you have multiple JDKs installed, make sure the correct version is specified in Installed JREs (Window → Preferences → Java → Installed JREs). Otherwise, Eclipse may not find the required compiler.

Cause 2: JRE System Library Does Not Match the Compliance Level

Sometimes the project has an old version of the JRE System Library (e.g., J2SE-1.4) specified, while your code uses annotations from Java 5+. Eclipse sees this mismatch and generates an error.

How to Fix:

\n
1. Right-click on the project → Build Path → Configure Build Path.
\n
2. Go to the Libraries tab.
\n
3. Find JRE System Library.
\n
4. Remove it (the Remove button).
\n
5. Click Add Library → JRE System Library → Next.
\n
6. Select Workspace default JRE (or the required JDK version).
\n
7. Click Finish and then Apply and Close.
\n
8. Clean the project: Project → Clean.
\n

Cause 3: Project Facets and Java Version Mismatch

In Eclipse, Project Facets (used for web applications, Maven, etc.) can also set a Java version. If the facet version is lower than what your code requires, the error will appear.

How to Fix:

\n
1. Right-click on the project → Properties.
\n
2. Go to Project Facets.
\n
3. Find Java in the list.
\n
4. Select the required version (e.g., 1.8 or 11).
\n
5. Click Apply and Close.
\n

Note: If the project uses Maven, you can also specify the version in the pom.xml file:

<properties>\n    <maven.compiler.source>1.8</maven.compiler.source>\n    <maven.compiler.target>1.8</maven.compiler.target>\n</properties>\n

After that, update the project: right-click → Maven → Update Project.

What to Do If Nothing Helps?

If you have tried all the methods, but the error persists, try the following:

\n
1. Delete the .metadata folder in the workspace (but be careful — this will reset all Eclipse settings).
\n
2. Create a new workspace and import the project again.
\n
3. Check the code: maybe you really are not overriding a method (e.g., a typo in the method signature).
\n
4. Use a different IDE: IntelliJ IDEA or NetBeans handle such situations more flexibly.
\n

Conclusion

The "Must Override a Superclass Method" error in Eclipse is most often caused by incorrect compiler settings, not by your code. By changing the Compiler compliance level or the JRE System Library, you can fix the problem in a couple of minutes.

Remember: if the code compiles successfully in another environment (Maven, IntelliJ IDEA), the issue is definitely in Eclipse. Don't rush to rewrite the code — just configure the environment correctly.

We hope this guide helped you. If you have questions or your own solutions, share them in the comments!