blocks|key|3133752|text|这意味着你正在尝试实现一个不存在的接口，或者你正在扩展一个不存在的类。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|3133753|尝试刷新您的Eclipse。|3133754|如果它不工作，这可能意味着您有一个不在构建路径中的对JAR的引用。检查项目的类路径，并验证包含接口或类的jar是否在其中。|3133755|entityMap^0|0|0|0^^$0|@$1|2|3|4|5|6|7|H|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|I|8|@]|9|@]|A|$]]|$1|D|3|E|5|6|7|J|8|@]|9|@]|A|$]]|$1|F|3|-4|5|6|7|K|8|@]|9|@]|A|$]]]|G|$]]

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.

blocks|key|3133852|text|有时，当您添加所需的jar，但不包括it所需的jar时，就会发生这种情况。在我的例子中，添加tomcat/lib中的所有jars帮助我解决了这个问题。我正在开发一个网络应用程序。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|3133853|entityMap^0|0^^$0|@$1|2|3|4|5|6|7|D|8|@]|9|@]|A|$]]|$1|B|3|-4|5|6|7|E|8|@]|9|@]|A|$]]]|C|$]]

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.

blocks|key|3133781|text|检查您的错误(“标记”选项卡)。我还遇到了以下错误：|type|unstyled|depth|inlineStyleRanges|entityRanges|data|3133782|无法读取项目中所需库的|3133783|存档...|blockquote|3133784|3133785|3133786|当这个问题得到解决时，“不一致错误”就消失了。|3133787|实际上，我已经将jars添加到了构建路径中，但是由于某种原因，它们无法被错误地读取|3133788|3133789|存档文件，或者该文件不是有效的ZIP文件|3133790|3133791|3133792|因此，我将它们添加为“外部Jars”。这很有帮助，所有的编译问题都不复存在了！|3133793|entityMap^0|0|0|0|0|0|0|0|0|0|0|0|0^^$0|@$1|2|3|4|5|6|7|V|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|W|8|@]|9|@]|A|$]]|$1|D|3|E|5|F|7|X|8|@]|9|@]|A|$]]|$1|G|3|-4|5|6|7|Y|8|@]|9|@]|A|$]]|$1|H|3|-4|5|6|7|Z|8|@]|9|@]|A|$]]|$1|I|3|J|5|6|7|10|8|@]|9|@]|A|$]]|$1|K|3|L|5|6|7|11|8|@]|9|@]|A|$]]|$1|M|3|C|5|6|7|12|8|@]|9|@]|A|$]]|$1|N|3|O|5|F|7|13|8|@]|9|@]|A|$]]|$1|P|3|-4|5|6|7|14|8|@]|9|@]|A|$]]|$1|Q|3|-4|5|6|7|15|8|@]|9|@]|A|$]]|$1|R|3|S|5|6|7|16|8|@]|9|@]|A|$]]|$1|T|3|-4|5|6|7|17|8|@]|9|@]|A|$]]]|U|$]]

Check your errors (tab "markers"). I had also the following error:

<blockquote>
 Archive for required library in project cannot be read...
</blockquote>

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

<blockquote>
 Archive for required library in project cannot be read or is not a valid ZIP file
</blockquote>

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

blocks|key|247850|text|在我将JDK升级到新版本后，我遇到了这个问题。我必须在Project+Properties/Java构建路径中更新对库的引用。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|247851|entityMap^0|0^^$0|@$1|2|3|4|5|6|7|D|8|@]|9|@]|A|$]]|$1|B|3|-4|5|6|7|E|8|@]|9|@]|A|$]]]|C|$]]

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.

blocks|key|3133985|text|我又接了一个案子。给出正确的项目路径，并将其导入eclipse。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|3133986|然后转到项目-->清理-->清理所有项目。|3133987|entityMap^0|0|0^^$0|@$1|2|3|4|5|6|7|F|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|G|8|@]|9|@]|A|$]]|$1|D|3|-4|5|6|7|H|8|@]|9|@]|A|$]]]|E|$]]

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

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

blocks|key|248165|text|您应该清理项目，或者重新启动Eclipse。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|248166|entityMap^0|0^^$0|@$1|2|3|4|5|6|7|D|8|@]|9|@]|A|$]]|$1|B|3|-4|5|6|7|E|8|@]|9|@]|A|$]]]|C|$]]

You should clean the project , or restart Eclipse.

blocks|key|2919529|text|如果类路径中的库文件中的某个类引用了另一个jar文件中不存在的类，您将看到此错误。在这里，当我没有添加org.springframework.beans-3.1.2.RELEASE.jar并且从org.springframework.jdbc.core.support.JdbcDaoSupport扩展了一个类时，我收到了这个错误，这个类位于我的类路径的org.springframework.jdbc-3.1.2.RELEASE.jar中。|type|unstyled|depth|inlineStyleRanges|offset|length|style|CODE|entityRanges|data|2919530|entityMap^0|1F|17|2P|1G|4X|16|0^^$0|@$1|2|3|4|5|6|7|H|8|@$9|I|A|J|B|C]|$9|K|A|L|B|C]|$9|M|A|N|B|C]]|D|@]|E|$]]|$1|F|3|-4|5|6|7|O|8|@]|D|@]|E|$]]]|G|$]]

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 <code>org.springframework.beans-3.1.2.RELEASE.jar</code> and had extended a class from <code>org.springframework.jdbc.core.support.JdbcDaoSupport</code>, which was in <code>org.springframework.jdbc-3.1.2.RELEASE.jar</code> of my classpath.

blocks|key|3133914|text|问题可能是您包含了不正确的jars。我遇到了同样的问题，原因是我在项目的构建路径中包含了不正确的默认JRE库。我用另一个版本安装了Java，并且包含了不同版本的Java的JRE文件。(我已经在我的系统中安装了JRE+1.6，由于之前安装了Java，所以JRE库1.7包含在构建路径中)您可以检查包含在构建路径中的JRE库是否具有正确的版本。已安装在系统中的Java版本。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|3133915|entityMap^0|0^^$0|@$1|2|3|4|5|6|7|D|8|@]|9|@]|A|$]]|$1|B|3|-4|5|6|7|E|8|@]|9|@]|A|$]]]|C|$]]

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.

blocks|key|2919681|text|我在Eclipse+Juno上遇到过这个问题，根本原因是尽管一些spring+jars包含在临时的maven依赖中，但它们包含在不正确的版本中。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|2919682|因此，您应该检查是否使用模块化框架作为spring，以确保每个模块(或者至少是最重要的:核心、beans、上下文、aop、tx等)都在同一版本中。|2919683|为了解决这个问题，我使用了maven依赖排除来避免瞬时依赖的错误版本。|2919684|entityMap^0|0|0|0^^$0|@$1|2|3|4|5|6|7|H|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|I|8|@]|9|@]|A|$]]|$1|D|3|E|5|6|7|J|8|@]|9|@]|A|$]]|$1|F|3|-4|5|6|7|K|8|@]|9|@]|A|$]]]|G|$]]

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.

blocks|key|2920321|text|错误："class+name“类型的层次结构不一致错误。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|2920322|解决方案："other.dep.jar"内部有class+OtherDepJar+{}+-->。|offset|length|style|BOLD|2920323|class+DepJar扩展了OtherDepJar+{}+-->在"dep.jar"中。|2920324|类ProblematicClass扩展了DepJar+{}+-->在当前项目中。|2920325|如果dep.jar在项目的类路径中，但other.dep.jar不在项目的类路径中，Eclipse将显示“the+hierarchy+of+The+type+...+is+inconsistent+error”|2920326|entityMap^0|0|5|F|T|B|0|6|6|F|B|Y|9|0|0|0^^$0|@$1|2|3|4|5|6|7|P|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|Q|8|@$D|R|E|S|F|G]|$D|T|E|U|F|G]]|9|@]|A|$]]|$1|H|3|I|5|6|7|V|8|@$D|W|E|X|F|G]|$D|Y|E|Z|F|G]|$D|10|E|11|F|G]]|9|@]|A|$]]|$1|J|3|K|5|6|7|12|8|@]|9|@]|A|$]]|$1|L|3|M|5|6|7|13|8|@]|9|@]|A|$]]|$1|N|3|-4|5|6|7|14|8|@]|9|@]|A|$]]]|O|$]]

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"

blocks|key|243066|text|对我来说，这个问题是由于错误的导入造成的。实际上，在添加v7支持库之后，需要更新导入。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|243067|可以通过对项目的每个类执行以下操作来修复该问题|243068|在导入的每个库中，使用android.[*]).删除所有行:从上下文菜单中选择/Organize+Imports或(CTRL%2BSHIFT%2BO)|offset|length|style|CODE|243069|When+prompted，然后选择库android.support.[*]+(而不是android.[*]).|ordered-list-item|243070|243071|entityMap^0|0|0|B|B|0|J|J|17|B|0|0^^$0|@$1|2|3|4|5|6|7|P|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|Q|8|@]|9|@]|A|$]]|$1|D|3|E|5|6|7|R|8|@$F|S|G|T|H|I]]|9|@]|A|$]]|$1|J|3|K|5|L|7|U|8|@$F|V|G|W|H|I]|$F|X|G|Y|H|I]]|9|@]|A|$]]|$1|M|3|-4|5|6|7|Z|8|@]|9|@]|A|$]]|$1|N|3|-4|5|6|7|10|8|@]|9|@]|A|$]]]|O|$]]

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:

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

blocks|key|246960|text|这肯定是因为缺少maven+pom.xml中没有的依赖项。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|246961|例如，我想为我的宽叶电子商务演示站点的实现创建集成测试。|246962|为了重用他们的配置文件和基本测试类，我已经包含了一个来自宽叶商业的集成测试的宽叶jar。该项目还有其他我没有包括的测试依赖项，并且我收到了“不一致的层次结构”错误。|246963|在从宽叶/pom.xml中复制“测试依赖项”和相关的属性变量之后，错误就消失了。|246964|这些属性包括：|246965|++++<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>|code-block|syntax|javascript|246966|依赖关系是：|246967|<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>
++++++++++++<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>
++
++++++++++++<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>|246968|entityMap^0|0|0|0|0|0|0|0|0^^$0|@$1|2|3|4|5|6|7|U|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|V|8|@]|9|@]|A|$]]|$1|D|3|E|5|6|7|W|8|@]|9|@]|A|$]]|$1|F|3|G|5|6|7|X|8|@]|9|@]|A|$]]|$1|H|3|I|5|6|7|Y|8|@]|9|@]|A|$]]|$1|J|3|K|5|L|7|Z|8|@]|9|@]|A|$M|N]]|$1|O|3|P|5|6|7|10|8|@]|9|@]|A|$]]|$1|Q|3|R|5|L|7|11|8|@]|9|@]|A|$M|N]]|$1|S|3|-4|5|6|7|12|8|@]|9|@]|A|$]]]|T|$]]

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:

<pre><code> &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;
</code></pre>

The dependencies were:

<pre><code>&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;
</code></pre>

blocks|key|2920137|text|如果扩展类有问题，则会显示上述错误消息。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|2920138|示例|2920139|class+Example+extends+Example1+{

}|code-block|syntax|javascript|2920140|修复Example1中的问题|offset|length|style|CODE|2920141|entityMap^0|0|0|0|2|8|0^^$0|@$1|2|3|4|5|6|7|Q|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|R|8|@]|9|@]|A|$]]|$1|D|3|E|5|F|7|S|8|@]|9|@]|A|$G|H]]|$1|I|3|J|5|6|7|T|8|@$K|U|L|V|M|N]]|9|@]|A|$]]|$1|O|3|-4|5|6|7|W|8|@]|9|@]|A|$]]]|P|$]]

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

Example 

<pre><code>class Example extends Example1 {

}
</code></pre>

fix the issues in <code>Example1</code>

blocks|key|3134340|text|我有相同的问题标记，并通过从一个方法中删除@Override注释来解决它，该方法实际上是第一个实现(“超级”方法是一个抽象方法)，而不是覆盖。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|3134341|entityMap^0|0^^$0|@$1|2|3|4|5|6|7|D|8|@]|9|@]|A|$]]|$1|B|3|-4|5|6|7|E|8|@]|9|@]|A|$]]]|C|$]]

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.

blocks|key|243293|text|在我的例子中，许多类中的导入引用都包含一个额外的单词。我通过编辑所有文件来获得正确的导入，从而解决了这个问题。我开始手动编辑。但是当我看到这个模式时，我用eclipse中的一个find..replace实现了自动化。这解决了错误。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|243294|entityMap^0|0^^$0|@$1|2|3|4|5|6|7|D|8|@]|9|@]|A|$]]|$1|B|3|-4|5|6|7|E|8|@]|9|@]|A|$]]]|C|$]]

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.

blocks|key|246830|text|对我来说，它将Android+API级别更改为带有Google+API的级别|type|unstyled|depth|inlineStyleRanges|entityRanges|data|246831|entityMap^0|0^^$0|@$1|2|3|4|5|6|7|D|8|@]|9|@]|A|$]]|$1|B|3|-4|5|6|7|E|8|@]|9|@]|A|$]]]|C|$]]

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

blocks|key|3134098|text|我也有这个问题...我发现抛出这个异常的类的层次结构不能通过eclipse追溯到它的根类……我来解释一下：|type|unstyled|depth|inlineStyleRanges|entityRanges|data|3134099|在我的例子中，我有3个java项目:+A、B和C……其中A和B是maven项目，C是常规的java+eclipse项目...|3134100|在项目A中，我有一个接口"interfaceA“...在项目B中，我有一个接口"interfaceB“来扩展项目C中的"interfaceA”，我有一个具体的类"classC“来实现"interfaceB”|3134101|“项目C”在其构建路径中包含了“项目B”，但没有包含“项目A”(所以这是导致错误的原因)……在将“项目A”包含在"C“的构建路径中之后，一切都恢复正常……|3134102|entityMap^0|0|0|0|0^^$0|@$1|2|3|4|5|6|7|J|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|K|8|@]|9|@]|A|$]]|$1|D|3|E|5|6|7|L|8|@]|9|@]|A|$]]|$1|F|3|G|5|6|7|M|8|@]|9|@]|A|$]]|$1|H|3|-4|5|6|7|N|8|@]|9|@]|A|$]]]|I|$]]

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...

blocks|key|2920085|text|我在一个使用OSGi的项目中有一个扩展LabelProvider的类，错误发生在那里。解决方案是:将org.eclipse.jface添加到manifest.mf中所需的插件中，而不是像org.eclipse.jface.viewers那样导入单个包|type|unstyled|depth|inlineStyleRanges|entityRanges|data|2920086|entityMap^0|0^^$0|@$1|2|3|4|5|6|7|D|8|@]|9|@]|A|$]]|$1|B|3|-4|5|6|7|E|8|@]|9|@]|A|$]]]|C|$]]

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

blocks|key|247098|text|如果您要导入eclipse项目，只需1.转到项目属性下的java+build+path设置。2.如果JRE系统库附加了错误标记，请双击它以打开Edit+library窗口。3.将执行环境更改为系统的正确java版本，或通过选中分配给它们的单选按钮选择编辑其他设置。4.点击finish|type|unstyled|depth|inlineStyleRanges|entityRanges|data|247099|entityMap^0|0^^$0|@$1|2|3|4|5|6|7|D|8|@]|9|@]|A|$]]|$1|B|3|-4|5|6|7|E|8|@]|9|@]|A|$]]]|C|$]]

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

blocks|key|243358|text|在没有安装"Google+Plugin+for+Eclipse“的情况下，在Eclipse中导入GWT项目时，会发生这种情况。安装"Google+Plugin+for+Eclipse“后，这个错误就会消失。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|243359|entityMap^0|0^^$0|@$1|2|3|4|5|6|7|D|8|@]|9|@]|A|$]]|$1|B|3|-4|5|6|7|E|8|@]|9|@]|A|$]]]|C|$]]

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.

blocks|key|245469|text|右键单击项目文件夹并选择"Java+Build+Path“。在"Java+Build+Path“下，您应该能够看到库。Eclipse将在其中任何一个库中显示错误。修复这些问题将有助于解决问题。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|245470|entityMap^0|0^^$0|@$1|2|3|4|5|6|7|D|8|@]|9|@]|A|$]]|$1|B|3|-4|5|6|7|E|8|@]|9|@]|A|$]]]|C|$]]

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.

blocks|key|2920402|text|在我的类扩展了一个新接口的分支中执行了一些git合并之后，我遇到了这个错误。在Eclipse的包资源管理器框架中使用文件树刷新(F5)文件树就足够了。|type|unstyled|depth|inlineStyleRanges|offset|length|style|BOLD|entityRanges|data|2920403|似乎Eclipse没有正确地更新所有内容，因此这些类扩展了一个不存在的接口。刷新后，所有错误都消失了。|2920404|entityMap^0|L|5|1B|6|0|0^^$0|@$1|2|3|4|5|6|7|J|8|@$9|K|A|L|B|C]|$9|M|A|N|B|C]]|D|@]|E|$]]|$1|F|3|G|5|6|7|O|8|@]|D|@]|E|$]]|$1|H|3|-4|5|6|7|P|8|@]|D|@]|E|$]]]|I|$]]

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.

blocks|key|3134516|text|我不得不从从IBM获得的Eclipse+Oxygen切换到Eclipse+Photon和OracleJDK8，我正在为maximo进行Java定制。|type|unstyled|depth|inlineStyleRanges|entityRanges|offset|length|data|3134517|entityMap|0|LINK|mutability|MUTABLE|url|/questions/tagged/maximo^0|1N|6|0|0^^$0|@$1|2|3|4|5|6|7|L|8|@]|9|@$A|M|B|N|1|O]]|C|$]]|$1|D|3|-4|5|6|7|P|8|@]|9|@]|C|$]]]|E|$F|$5|G|H|I|C|$J|K]]]]

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 <a href="/questions/tagged/maximo" class="post-tag" title="show questions tagged &#39;maximo&#39;" rel="tag">maximo</a>.

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?

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

集成测试

Android

Eclipse

Java

我下载了一些用Java编写的开源软件，并尝试使用Eclipse进行编译。我在一些文件中收到错误："The hierarchy of the type 'Class name‘is inconsistent“。是什么导致了这些错误?我该如何修复它们？

问Eclipse编译错误:类型'Class name‘的层次结构不一致
EN

回答 23

Stack Overflow用户

Stack Overflow用户

Stack Overflow用户

社区

活动

资源

关于

腾讯云开发者

热门产品

热门推荐

更多推荐

问Eclipse编译错误:类型'Class name‘的层次结构不一致EN

回答 23

Stack Overflow用户

Stack Overflow用户

Stack Overflow用户

社区

活动

资源

关于

腾讯云开发者

热门产品

热门推荐

更多推荐

问Eclipse编译错误:类型'Class name‘的层次结构不一致
EN