Eclipse compilation error: The hierarchy of the type 'Class name' is inconsistent

JavaEclipse

Java Problem Overview

I have downloaded some open source software written in Java and tried to compile it using Eclipse. I got the error: "The hierarchy of the type 'Class name' is inconsistent" in some files. What causes these errors and how do I fix them?

Java Solutions

Solution 1 - Java

It means you are trying to implement a non-existing interface or you're extending an non-existing class.

Try to refresh your Eclipse.

If it doesn't work, it may mean that you have a reference to a JAR that is not in the build path. Check your project's classpath and verify that the jar containing the interface or the class is in it.

Solution 2 - Java

Sometimes it happens when you add a jar that YOU need, but don't include the jars that IT needs. In my case adding all the jars in tomcat/lib helped me to solve this problem. I am working on a web-app.

Solution 3 - Java

Check your errors (tab "markers"). I had also the following error: > Archive for required library in project cannot be read...

and when that was fixed the "inconsistent-error" disappeared.

Actually I had added jars to the build path, but for some reason they could not be read with error > Archive for required library in project cannot be read or is not a valid ZIP file

So instead I added them as "External Jars". That helped and all compilation problems were no more!

Solution 4 - Java

I had this problem after I upgraded the JDK to a new version. I had to update the references to libraries in Project Properties/Java Build Path.

Solution 5 - Java

One more case I have had. Give the correct project path, and import it to eclipse.

Then go to Project--> Clean --> Clean all projects.

Solution 6 - Java

You should clean the project , or restart Eclipse.

Solution 7 - Java

You will see this error in case a some class in your library file you have in classpath has reference to non-existing classe(s) which could be in another jar file. Here, I received this error when I did not add org.springframework.beans-3.1.2.RELEASE.jar and had extended a class from org.springframework.jdbc.core.support.JdbcDaoSupport, which was in org.springframework.jdbc-3.1.2.RELEASE.jar of my classpath.

Solution 8 - Java

The problem may be that you have included incorrect jars. I had the same problem and the reason was that I had included incorrect default JRE library in the build path of the project. I had installed Java with another version and was including JRE files of Java with a different version. (I had installed JRE 1.6 in my system and was having JRE library 1.7 included in the build path due to previously installed Java) May be you can check if the JRE library that you have included in the build path is of correct version ie. of Java version that you have installed in your system.

Solution 9 - Java

I 've experienced this problem on Eclipse Juno, the root cause was that although some spring jars were being included by transient maven dependencies they were included in incorrect versions.

So you should check if using a modularized framework as spring that every module (or at least the most important: core, beans, context, aop, tx, etc.) are in the same version.

To solve the problem I 've used maven dependnecy exclusions to avoid incorrect version of transient dependencies.

Solution 10 - Java

Error : the hierarchy of the type "class name" is inconsistent error.

solution : class OtherDepJar {} --> is inside "other.dep.jar" .

class DepJar extends OtherDepJar {} --> is inside "dep.jar".

class ProblematicClass extends DepJar {} --> is inside current project .

If dep.jar is in the project's classpath, but other.dep.jar isn't in the project's classpath, Eclipse will show the" The hierarchy of the type ... is inconsistent error"

Solution 11 - Java

To me, the issue was due to wrong imports. In fact, one need to update the imports after adding the v7 support library.

It can be fixed by doing as follows, for each class of your project:

  1. Delete all the lines with import android.[*], in each class
  2. Reorganize your imports: from the context menu select Source/Organize Imports or (CTRL+SHIFT+O)
  3. When prompted, select the libraries android.support.[*] (and not android.[*]).

Solution 12 - Java

It was definitely because missing dependencies that were not in my maven pom.xml.

For example, I wanted to create integration tests for my implementation of the broadleaf ecommerce demo site.

I had included a broadleaf jar with integration tests from broadleaf commerce in order to reuse their configuration files and base testing classes. That project had other testing dependencies that I had not included and I received the "inconsistent hierarchy" error.

After copying the "test dependencies" from broadleaf/pom.xml and the associated properties variables that provided the versions for each dependency in broadleaf/pom.xml, the error went away.

The properties were:

    <geb.version>0.9.3</geb.version>
	<spock.version>0.7-groovy-2.0</spock.version>
	<selenium.version>2.42.2</selenium.version>
	<groovy.version>2.1.8</groovy.version>

The dependencies were:

<dependency>
			<groupId>org.broadleafcommerce</groupId>
			<artifactId>integration</artifactId>
			<type>jar</type>
			<classifier>tests</classifier>
			<scope>test</scope>
		</dependency>
		<dependency>
			<groupId>org.broadleafcommerce</groupId>
			<artifactId>broadleaf-framework</artifactId>
			<version>${blc.version}</version><!--$NO-MVN-MAN-VER$ -->
			<classifier>tests</classifier>
		</dependency>
        <dependency>
			<groupId>com.icegreen</groupId>
			<artifactId>greenmail</artifactId>
			<version>1.3</version>
			<type>jar</type>
			<scope>test</scope>
		</dependency>
		<dependency>
			<groupId>junit</groupId>
			<artifactId>junit</artifactId>
			<version>4.11</version>
			<scope>test</scope>
		</dependency>
		<dependency>
			<groupId>org.easymock</groupId>
			<artifactId>easymock</artifactId>
			<version>2.5.1</version>
			<type>jar</type>
			<scope>test</scope>
		</dependency>
		<dependency>
			<groupId>org.easymock</groupId>
			<artifactId>easymockclassextension</artifactId>
			<version>2.4</version>
			<type>jar</type>
			<scope>test</scope>
		</dependency>
		<dependency>
			<groupId>org.testng</groupId>
			<artifactId>testng</artifactId>
			<version>5.9</version>
			<type>jar</type>
			<classifier>jdk15</classifier>
			<scope>test</scope>
		</dependency>
		<dependency>
			<groupId>org.codehaus.groovy</groupId>
			<artifactId>groovy-all</artifactId>
			<version>${groovy.version}</version>
			<scope>test</scope>
		</dependency>
		<dependency>
			<groupId>org.gebish</groupId>
			<artifactId>geb-core</artifactId>
			<version>${geb.version}</version>
			<scope>test</scope>
		</dependency>
		<dependency>
			<groupId>org.gebish</groupId>
			<artifactId>geb-spock</artifactId>
			<version>${geb.version}</version>
			<scope>test</scope>
		</dependency>
		<dependency>
			<groupId>org.spockframework</groupId>
			<artifactId>spock-core</artifactId>
			<version>${spock.version}</version>
			<scope>test</scope>
		</dependency>
		<dependency>
			<groupId>org.seleniumhq.selenium</groupId>
			<artifactId>selenium-support</artifactId>
			<version>${selenium.version}</version>
			<scope>test</scope>
		</dependency>
		<dependency>
			<groupId>org.seleniumhq.selenium</groupId>
			<artifactId>selenium-firefox-driver</artifactId>
			<version>${selenium.version}</version>
			<scope>test</scope>
		</dependency>
		<dependency>
			<groupId>org.seleniumhq.selenium</groupId>
			<artifactId>selenium-chrome-driver</artifactId>
			<version>${selenium.version}</version>
			<scope>test</scope>
		</dependency>
  <!-- Logging -->
            <dependency>
                <groupId>log4j</groupId>
                <artifactId>log4j</artifactId>
                <version>1.2.12</version>
                <type>jar</type>
                <scope>test</scope>
            </dependency>
            <dependency>
                <groupId>org.slf4j</groupId>
                <artifactId>slf4j-log4j12</artifactId>
                <version>1.6.1</version>
                <type>jar</type>
                <scope>test</scope>
            </dependency>
            <dependency>
                <groupId>org.slf4j</groupId>
                <artifactId>jcl-over-slf4j</artifactId>
                <version>1.6.1</version>
                <type>jar</type>
                <scope>test</scope>
            </dependency>
            <dependency>
                <groupId>org.slf4j</groupId>
                <artifactId>slf4j-api</artifactId>
                <version>1.6.1</version>
                <type>jar</type>
                <scope>test</scope>
            </dependency>
            <dependency>
                <groupId>org.hsqldb</groupId>
                <artifactId>hsqldb</artifactId>
                <version>2.3.1</version>
                <type>jar</type>
                <scope>test</scope>
            </dependency>

Solution 13 - Java

If the extended class has the issue then the above error message will gets displayed.

Example

class Example extends Example1 {

}

fix the issues in Example1

Solution 14 - Java

I had the same exact problem marker and solved it by removing the @Override annotation from a method that was in fact the first implementation (the "super" one being an abstract method) and not an override.

Solution 15 - Java

In my case, the import references in many of the classes contained an extra word. I solved it by editing all the files to have the correct imports. I started doing the edits manually. But when I saw the pattern, I automated it with a find..replace in eclipse. This resolved the error.

Solution 16 - Java

For me it was changing the Android API level to one with Google APIs

Solution 17 - Java

I was having this problem too... I found out that the hierarchy of the class that was throwing this exception, cannot be traced all way back to its root class by eclipse... I Explain:

In my case, I have 3 java project: A, B and C... where A and B are maven projects and C a regular java eclipse project...

In the project A, i have the interface "interfaceA" ... In the project B, i have the interface "interfaceB" that extends "interfaceA" In the project C, i have the concrete class "classC" that implements "interfaceB"

The "project C" was including the "project B" in its build path but not "project A" (so that was the cause of the error).... After including "project A" inside the build path of "C", everything went back to normal...

Solution 18 - Java

I had a class that extends LabelProvider in a project with OSGi, there the error occured. The solution was: Adding org.eclipse.jface to the required plugins in the manifest.mf instead of importing the single packages like org.eclipse.jface.viewers

Solution 19 - Java

if you are importing the eclipse project just

  1. Go to the java build path setting under the project properties.
  2. In case the JRE System library has an error sign attach to it double click it to open the Edit library window
  3. Change the execution environment to the correct java version of the system or choose edit the other settings by checking the radio buttons assign to them.
  4. Click finish

Solution 20 - Java

When importing a GWT project in Eclipse without installing "Google Plugin for Eclipse", this will occur. After installing "Google Plugin for Eclipse", this error will disappear.

Solution 21 - Java

Right click on the project folder and select "Java Build Path". Under "Java Build Path" you should be able to see libraries. Eclipse will show errors in any of those libraries. Fixing those issue will help to resolve the issue.

Solution 22 - Java

I had this error after doing some git merge from a branch where my classes extended a new interface. It was enough to Refresh (F5) the File-Tree in the Package Explorer frame of Eclipse.

It seems that Eclipse did not update everything properly and so the classes were extending a non-existing-yet interface. After refresh, all errors disappeared.

Solution 23 - Java

I had to switch from Eclipse Oxygen that I got from IBM and used IBM JDK 8 to Eclipse Photon and Oracle JDK 8. I'm working on Java customizations for [tag:maximo].

Categories
Recommended Java Solutions
Recommended Eclipse Solutions

Previous Solution:

How to create the branch from specific commit in different branch

GitGit Branch

Next Solution:

How to represent empty char in Java Character class

Java

Attributions

All content for this solution is sourced from the original question on Stackoverflow.

The content on this page is licensed under the Attribution-ShareAlike 4.0 International (CC BY-SA 4.0) license.

Content TypeOriginal AuthorOriginal Content on Stackoverflow
Questionuser1099579View Question on Stackoverflow
Solution 1 - JavaLaGrandMereView Answer on Stackoverflow
Solution 2 - JavaIbolitView Answer on Stackoverflow
Solution 3 - JavaJohan ValentinView Answer on Stackoverflow
Solution 4 - JavajmstView Answer on Stackoverflow
Solution 5 - JavaAshokchakravarthi NagarajanView Answer on Stackoverflow
Solution 6 - JavaAnh ThuView Answer on Stackoverflow
Solution 7 - JavaJames JithinView Answer on Stackoverflow
Solution 8 - JavapritiView Answer on Stackoverflow
Solution 9 - JavaNicolas BarreraView Answer on Stackoverflow
Solution 10 - Javavijay m pView Answer on Stackoverflow
Solution 11 - JavaLuca FagioliView Answer on Stackoverflow
Solution 12 - JavaBobView Answer on Stackoverflow
Solution 13 - Javauser3195324View Answer on Stackoverflow
Solution 14 - JavaLaurenţiu LozanView Answer on Stackoverflow
Solution 15 - JavaCodeMedView Answer on Stackoverflow
Solution 16 - JavaFernando GallegoView Answer on Stackoverflow
Solution 17 - JavaCarlitos WayView Answer on Stackoverflow
Solution 18 - JavaHarry SiebertView Answer on Stackoverflow
Solution 19 - JavamumbasaView Answer on Stackoverflow
Solution 20 - JavaTomView Answer on Stackoverflow
Solution 21 - JavaMR ANDView Answer on Stackoverflow
Solution 22 - JavanhaggenView Answer on Stackoverflow
Solution 23 - JavaPreacherView Answer on Stackoverflow