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

Question

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

User · Answer

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

User · Answer

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

User · Answer

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

User · Answer

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

User · Answer

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    Delete all the lines with import android      in each class Reorganize your imports  from the context menu select Source Organize Imports or  CTRL SHIFT O  When prompted  select the libraries android support      and not android

User · Answer

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

User · Answer

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

User · Answer

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

User · Answer

You should clean the project   or restart Eclipse

User · Answer

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

User · Answer

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

User · Answer

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

User · Answer

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

User · Answer

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

User · Answer

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

User · Answer

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

User · Answer

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 maximo

User · Answer

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

User · Answer

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

User · Answer

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

User · Answer

One more case I have had  Give the correct project path  and import it to  eclipse   Then go to Project--  Clean --  Clean all projects

User · Answer

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

User · Answer

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        lt geb version gt 0 9 3 lt  geb version gt       lt spock version gt 0 7-groovy-2 0 lt  spock version gt       lt selenium version gt 2 42 2 lt  selenium version gt       lt groovy version gt 2 1 8 lt  groovy version gt    The dependencies were    lt dependency gt               lt groupId gt org broadleafcommerce lt  groupId gt               lt artifactId gt integration lt  artifactId gt               lt type gt jar lt  type gt               lt classifier gt tests lt  classifier gt               lt scope gt test lt  scope gt           lt  dependency gt           lt dependency gt               lt groupId gt org broadleafcommerce lt  groupId gt               lt artifactId gt broadleaf-framework lt  artifactId gt               lt version gt   blc version  lt  version gt  lt  -- NO-MVN-MAN-VER  -- gt               lt classifier gt tests lt  classifier gt           lt  dependency gt           lt dependency gt               lt groupId gt com icegreen lt  groupId gt               lt artifactId gt greenmail lt  artifactId gt               lt version gt 1 3 lt  version gt               lt type gt jar lt  type gt               lt scope gt test lt  scope gt           lt  dependency gt           lt dependency gt               lt groupId gt junit lt  groupId gt               lt artifactId gt junit lt  artifactId gt               lt version gt 4 11 lt  version gt               lt scope gt test lt  scope gt           lt  dependency gt           lt dependency gt               lt groupId gt org easymock lt  groupId gt               lt artifactId gt easymock lt  artifactId gt               lt version gt 2 5 1 lt  version gt               lt type gt jar lt  type gt               lt scope gt test lt  scope gt           lt  dependency gt           lt dependency gt               lt groupId gt org easymock lt  groupId gt               lt artifactId gt easymockclassextension lt  artifactId gt               lt version gt 2 4 lt  version gt               lt type gt jar lt  type gt               lt scope gt test lt  scope gt           lt  dependency gt           lt dependency gt               lt groupId gt org testng lt  groupId gt               lt artifactId gt testng lt  artifactId gt               lt version gt 5 9 lt  version gt               lt type gt jar lt  type gt               lt classifier gt jdk15 lt  classifier gt               lt scope gt test lt  scope gt           lt  dependency gt           lt dependency gt               lt groupId gt org codehaus groovy lt  groupId gt               lt artifactId gt groovy-all lt  artifactId gt               lt version gt   groovy version  lt  version gt               lt scope gt test lt  scope gt           lt  dependency gt           lt dependency gt               lt groupId gt org gebish lt  groupId gt               lt artifactId gt geb-core lt  artifactId gt               lt version gt   geb version  lt  version gt               lt scope gt test lt  scope gt           lt  dependency gt           lt dependency gt               lt groupId gt org gebish lt  groupId gt               lt artifactId gt geb-spock lt  artifactId gt               lt version gt   geb version  lt  version gt               lt scope gt test lt  scope gt           lt  dependency gt           lt dependency gt               lt groupId gt org spockframework lt  groupId gt               lt artifactId gt spock-core lt  artifactId gt               lt version gt   spock version  lt  version gt               lt scope gt test lt  scope gt           lt  dependency gt           lt dependency gt               lt groupId gt org seleniumhq selenium lt  groupId gt               lt artifactId gt selenium-support lt  artifactId gt               lt version gt   selenium version  lt  version gt               lt scope gt test lt  scope gt           lt  dependency gt           lt dependency gt               lt groupId gt org seleniumhq selenium lt  groupId gt               lt artifactId gt selenium-firefox-driver lt  artifactId gt               lt version gt   selenium version  lt  version gt               lt scope gt test lt  scope gt           lt  dependency gt           lt dependency gt               lt groupId gt org seleniumhq selenium lt  groupId gt               lt artifactId gt selenium-chrome-driver lt  artifactId gt               lt version gt   selenium version  lt  version gt               lt scope gt test lt  scope gt           lt  dependency gt     lt  -- Logging -- gt               lt dependency gt                   lt groupId gt log4j lt  groupId gt                   lt artifactId gt log4j lt  artifactId gt                   lt version gt 1 2 12 lt  version gt                   lt type gt jar lt  type gt                   lt scope gt test lt  scope gt               lt  dependency gt               lt dependency gt                   lt groupId gt org slf4j lt  groupId gt                   lt artifactId gt slf4j-log4j12 lt  artifactId gt                   lt version gt 1 6 1 lt  version gt                   lt type gt jar lt  type gt                   lt scope gt test lt  scope gt               lt  dependency gt               lt dependency gt                   lt groupId gt org slf4j lt  groupId gt                   lt artifactId gt jcl-over-slf4j lt  artifactId gt                   lt version gt 1 6 1 lt  version gt                   lt type gt jar lt  type gt                   lt scope gt test lt  scope gt               lt  dependency gt               lt dependency gt                   lt groupId gt org slf4j lt  groupId gt                   lt artifactId gt slf4j-api lt  artifactId gt                   lt version gt 1 6 1 lt  version gt                   lt type gt jar lt  type gt                   lt scope gt test lt  scope gt               lt  dependency gt               lt dependency gt                   lt groupId gt org hsqldb lt  groupId gt                   lt artifactId gt hsqldb lt  artifactId gt                   lt version gt 2 3 1 lt  version gt                   lt type gt jar lt  type gt                   lt scope gt test lt  scope gt               lt  dependency gt

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

Examples related to java

Examples related to eclipse