blocks|key|275090|text|它的意思是：“您使用的类需要另一个不在类路径上的类。”您应该确保(如Harry+Joy建议的那样)将所需的jar添加到类路径中。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|275091|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|$]]

It means: "A class that you use needs another class that is not on the classpath." You should make sure (as Harry Joy suggests) to add the required jar to the classpath.

blocks|key|273568|text|这很可能是Eclipse混淆的问题，因为这是一个实际的错误。我忽略了这个错误，并运行了它所抱怨的endpointInterface的web服务，它运行得很好，除了每次我想要运行它时都必须处理对话框。这只是另一个不透明的错误，什么也没告诉我。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|273569|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|$]]

This is as likely a matter of Eclipse's getting confused as it is an actual error. I ignored the error and ran the web service whose endpointInterface it complained about, and it ran fine, except for having to deal with the dialog every time I wanted to run it. Just another opaque error that tells me nothing.

blocks|key|2976610|text|它有时会发生在我身上，我总是用"mvn+eclipse:+clean“命令来修复这个问题，清除旧的属性，然后运行mvn+eclipse:eclipse+-Dwtpversion=2.0+(当然是web项目)。由于保存了一些旧的属性，所以eclipse有时会被混淆。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|2976611|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|$]]

It happens to me sometimes, I always fixed that with "mvn eclipse:clean" command to clean old properties and then run mvn eclipse:eclipse -Dwtpversion=2.0 (for web project of course). There are some old properties saved so eclipse is confused sometimes.

blocks|key|277263|text|我出现这个错误是因为损坏了本地maven存储库。|type|unstyled|depth|inlineStyleRanges|offset|length|style|BOLD|entityRanges|data|277264|因此，为了解决这个问题，我所要做的就是进入我的存储库，删除相关.jar所在的文件夹，然后在Eclipse中强制执行一个update+maven。|CODE|277265|entityMap^0|A|D|0|1N|C|0^^$0|@$1|2|3|4|5|6|7|K|8|@$9|L|A|M|B|C]]|D|@]|E|$]]|$1|F|3|G|5|6|7|N|8|@$9|O|A|P|B|H]]|D|@]|E|$]]|$1|I|3|-4|5|6|7|Q|8|@]|D|@]|E|$]]]|J|$]]

I had this error because of a corrupted local maven repository.

So, in order to fix the problem, all I had to do was going in my repository and delete the folder where the concerned .jar was, then force an <code>update maven</code> in Eclipse.

blocks|key|3190523|text|这听起来像是一个已知的问题(错误67414)，已经在3.0中解决了……有人评论说，在3.4版本中也会发生这种情况。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|3190524|同时，解决办法是从项目中删除JRE系统库，然后重新添加它。|3190525|Here+are+the+steps:|code-block|syntax|javascript|3190526|转到带有构建错误的项目的属性(右键单击>属性)|3190527|查看“构建路径”部分中的“库”选项卡|3190528|在列表中找到"JRE系统库“(如果缺少该库，则此错误消息不是eclipse错误，而是一个配置错误的项目)|3190529|删除"JRE系统库“|3190530|点击“添加库..."，选择"JRE系统库”并为项目添加适当的JRE+(例如：‘工作区默认JRE')|3190531|在库选择中单击"Finish“，在项目属性中单击"OK”，然后等待项目的重新生成|3190532|希望这个错误能被解决。|3190533|entityMap^0|0|0|0|0|0|0|0|0|0|0^^$0|@$1|2|3|4|5|6|7|Y|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|Z|8|@]|9|@]|A|$]]|$1|D|3|E|5|F|7|10|8|@]|9|@]|A|$G|H]]|$1|I|3|J|5|6|7|11|8|@]|9|@]|A|$]]|$1|K|3|L|5|6|7|12|8|@]|9|@]|A|$]]|$1|M|3|N|5|6|7|13|8|@]|9|@]|A|$]]|$1|O|3|P|5|6|7|14|8|@]|9|@]|A|$]]|$1|Q|3|R|5|6|7|15|8|@]|9|@]|A|$]]|$1|S|3|T|5|6|7|16|8|@]|9|@]|A|$]]|$1|U|3|V|5|6|7|17|8|@]|9|@]|A|$]]|$1|W|3|-4|5|6|7|18|8|@]|9|@]|A|$]]]|X|$]]

It sounds like this has been a known issue (Bug 67414)that was resolved in 3.0 ... someone has commented that it's occurring for them in 3.4 as well. 

In the mean time, the work around is to remove the JRE System Library from the project and then add it back again. 

<pre><code>Here are the steps:
</code></pre>

Go to properties of project with the build error (right click > Properties)

View the "Libraries" tab in the "Build Path" section

Find the "JRE System Library" in the list (if this is missing then this error message is not an eclipse bug but a mis-configured project)

Remove the "JRE System Library"

Hit "Add Library ...", Select "JRE System Library" and add the appropriate JRE for the project (eg. 'Workspace default JRE')

Hit "Finish" in the library selection and "OK" in the project properties and then wait for the re-build of the project

Hopefully the error will be resolved ...

blocks|key|275138|text|当jar文件中的类不遵循与jar文件夹结构相同的结构时，就会出现此错误。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|275139|例如，如果您的类文件具有包com.test.exam，而从此类文件创建的classes.jar具有结构test.exam...将抛出错误。您需要更正classes.jar的包结构，然后将其包含在ecplipse构建路径中……|275140|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|$]]

This error occurs when the classes in the jar file does not follow the same structure as of the folder structure of the jar..

e.g. if you class file has package com.test.exam and the classes.jar created out of this class file has structure test.exam... error will be thrown. You need to correct the package structure of your classes.jar and then include it in ecplipse build path...

blocks|key|277208|text|我得到这个异常是因为eclipse在不同版本的jdk中工作，只是更改为正确的、干净的和构建的，并且工作了！|type|unstyled|depth|inlineStyleRanges|entityRanges|data|277209|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 got this exception because eclipse was working in a different version of jdk, just changed to the correct, clean and build and worked!

blocks|key|3190778|text|我在Eclipse4.4.2中遇到过一个有趣的问题。我的项目(P1)引用了一个外部类(项目P2)，其中包含两个名称相同但参数类型不同的方法：|type|unstyled|depth|inlineStyleRanges|entityRanges|data|3190779|public+static+void+setItem(Integer+id)+…
public+static+void+setItem(Item+item)+…|code-block|syntax|javascript|3190780|类型Item包含在第三个项目P3中，我不希望它在这里可见。P1只调用了第一个方法：|offset|length|style|CODE|3190781|ExternalClass.setItem(Integer.valueOf(12345));|3190782|因此，没有使用使用Item类的第二个方法，而且P3确实不在编译类路径中-如果不使用它，为什么还要使用它。|3190783|但是Eclipse告诉我|3190784|The+type+...Item+cannot+be+resolved.
It+is+indirectly+referenced+from+required+.class+files|3190785|从命令行编译不会产生任何此类问题。更改第二个方法的名称(此处未使用！)在Eclipse中也解决了这个问题。|3190786|entityMap^0|0|0|2|4|0|0|9|4|0|0|0|0^^$0|@$1|2|3|4|5|6|7|Y|8|@]|9|@]|A|$]]|$1|B|3|C|5|D|7|Z|8|@]|9|@]|A|$E|F]]|$1|G|3|H|5|6|7|10|8|@$I|11|J|12|K|L]]|9|@]|A|$]]|$1|M|3|N|5|D|7|13|8|@]|9|@]|A|$E|F]]|$1|O|3|P|5|6|7|14|8|@$I|15|J|16|K|L]]|9|@]|A|$]]|$1|Q|3|R|5|6|7|17|8|@]|9|@]|A|$]]|$1|S|3|T|5|D|7|18|8|@]|9|@]|A|$E|F]]|$1|U|3|V|5|6|7|19|8|@]|9|@]|A|$]]|$1|W|3|-4|5|6|7|1A|8|@]|9|@]|A|$]]]|X|$]]

I had an interesting case of this problem with Eclipse 4.4.2. My project (P1) referenced an external class (project P2) with two methods with the same name but different argument types:

<pre><code>public static void setItem(Integer id) …
public static void setItem(Item item) …
</code></pre>

The type <code>Item</code> was contained in a third project P3, which I did not want to be visible here. P1 called only the first method:

<pre><code>ExternalClass.setItem(Integer.valueOf(12345));
</code></pre>

So the second method, which used the <code>Item</code> class, was not used, and it is true that P3 was not in the compilation classpath – why should it if it is not used.

Still Eclipse told me

<pre><code>The type ...Item cannot be resolved.
It is indirectly referenced from required .class files
</code></pre>

Compiling from the command line did not produce any such issues. Changing the name of the second method (unused here!) made the problem go away in Eclipse, too.

blocks|key|273587|text|如果您仍然找不到设置中的任何错误，您可以尝试项目->清理和清理工作区中的所有项目。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|273588|编辑:对不起，没有看到verbose_mode的建议...同样的事情|273589|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|$]]

If you still can not find anything wrong with your setup, you can try Project -> Clean and clean all the projects in the workspace.

EDIT: Sorry, did not see the suggestion of verbose_mode ... same thing

blocks|key|3190815|text|为我解决这个问题的是right+clicking+on+project+>+Maven+>+Update+Project|type|unstyled|depth|inlineStyleRanges|offset|length|style|CODE|entityRanges|data|3190816|entityMap^0|A|1E|0^^$0|@$1|2|3|4|5|6|7|H|8|@$9|I|A|J|B|C]]|D|@]|E|$]]|$1|F|3|-4|5|6|7|K|8|@]|D|@]|E|$]]]|G|$]]

What fixed it for me was <code>right clicking on project &gt; Maven &gt; Update Project</code>

blocks|key|2976782|text|对我来说，当我将我的jdk升级到1.8.0_60时就会发生这种情况，因为我的旧jars集已经使用了很长时间。如果我退回到jdk1.7.0_25，所有这些问题都会消失。这似乎是关于JRE和库之间的兼容性的问题。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|2976783|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 happens when I upgrade my jdk to 1.8.0_60 with my old set of jars has been used for long time. If I fall back to jdk1.7.0_25, all these problem are gone. It seems a problem about the compatibility between the JRE and the libraries.

blocks|key|2976599|text|当我只是更改了一些svn设置，而没有更改代码中的任何内容时，我得到了这个错误。只需清理项目即可修复错误。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|2976600|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 got the error when I just changing some svn settings and not anything in the code. Just cleaning the projects fixed the error.

blocks|key|273635|text|在我的例子中，我创建了一个项目，并创建了它的minSdkVersion=9和targetSdkVersion=17。我使用的是自动生成的libs/android-support-v4.jar。我还必须通过android-support-v7-appcomapt.jar来使用ActionBarActivity。所以我只是从android-sdk/extras/andrid/support/v7/appcompat/libs文件夹复制了android-support-v7-appcompat.jar文件并将其粘贴到我的项目libs文件夹中。这导致了上面的错误。所以基本上，我还需要将android-sdk/extras/andrid/support/v7/appcompat/libs中的android-support-v4.jar文件放到我的项目libs文件夹中。据我所知，v7.jar文件依赖于v4.jar文件。所以，它需要它自己的v4.jar文件，而不是我的项目，自动创建v4.jar文件。|type|unstyled|depth|inlineStyleRanges|offset|length|style|CODE|entityRanges|data|273636|entityMap^0|M|F|12|J|1W|R|2U|W|3T|H|4H|1F|62|W|7A|4|84|1F|9L|M|AF|4|AT|6|B4|6|BN|6|C8|6|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]|$9|O|A|P|B|C]|$9|Q|A|R|B|C]|$9|S|A|T|B|C]|$9|U|A|V|B|C]|$9|W|A|X|B|C]|$9|Y|A|Z|B|C]|$9|10|A|11|B|C]|$9|12|A|13|B|C]|$9|14|A|15|B|C]|$9|16|A|17|B|C]|$9|18|A|19|B|C]|$9|1A|A|1B|B|C]]|D|@]|E|$]]|$1|F|3|-4|5|6|7|1C|8|@]|D|@]|E|$]]]|G|$]]

In my case ,I created a project and made its <code>minSdkVersion=9</code> and <code>targetSdkVersion=17</code>. I used automatically generated <code>libs/android-support-v4.jar</code>. I also had to make use of <code>ActionBarActivity</code> using <code>android-support-v7-appcomapt.jar</code>. So I just copied the <code>android-support-v7-appcompat.jar</code> file from <code>android-sdk/extras/andrid/support/v7/appcompat/libs</code> folder and pasted it to my project <code>libs</code> folder. And this caused the above error. 
So basically,I needed to put <code>android-support-v4.jar</code> file from <code>android-sdk/extras/andrid/support/v7/appcompat/libs</code> as well to my project <code>libs</code> folder. As per my knowledge the <code>v7.jar</code> file had dependencies on <code>v4.jar</code> file. So ,it needed it own <code>v4.jar</code>file,instead of my project,automatically created <code>v4.jar</code> file.

blocks|key|2976684|text|我以这种方式快速简单地修复了它(我在Windows+XP家庭版上使用ADT版本:+v21.0.0-531062+)|type|unstyled|depth|inlineStyleRanges|entityRanges|data|2976685|2976686|已打开清单文件。|ordered-list-item|2976687|将现有项目minSdkVersion更改为与maxSdkVersion相同的值(建议:创建新项目并查看它的maxSdkVersion是什么可能很好)|2976688|保存清单文件。|2976689|右键单击该项目并选择生成项目。|2976690|从顶部菜单:项目-清理。-只选中相关项目，下面我勾选了Start+a+Build+immediately+and+build+only+the+selected+projects和OK。|2976691|打开java文件-不再出现红色错误！|2976692|返回到上面的步骤1并将minSdkVersion更改回其原始值(以支持尽可能多的安卓版本)。|2976693|2976694|它起作用了，但问题每隔几天就会出现一次。我做了与上面相同的操作，它解决了问题并让我进行开发。|2976695|entityMap^0|0|0|0|0|0|0|0|0|0|0|0^^$0|@$1|2|3|4|5|6|7|W|8|@]|9|@]|A|$]]|$1|B|3|-4|5|6|7|X|8|@]|9|@]|A|$]]|$1|C|3|D|5|E|7|Y|8|@]|9|@]|A|$]]|$1|F|3|G|5|E|7|Z|8|@]|9|@]|A|$]]|$1|H|3|I|5|E|7|10|8|@]|9|@]|A|$]]|$1|J|3|K|5|E|7|11|8|@]|9|@]|A|$]]|$1|L|3|M|5|E|7|12|8|@]|9|@]|A|$]]|$1|N|3|O|5|E|7|13|8|@]|9|@]|A|$]]|$1|P|3|Q|5|E|7|14|8|@]|9|@]|A|$]]|$1|R|3|-4|5|6|7|15|8|@]|9|@]|A|$]]|$1|S|3|T|5|6|7|16|8|@]|9|@]|A|$]]|$1|U|3|-4|5|6|7|17|8|@]|9|@]|A|$]]]|V|$]]

Quickly and Simply I fixed it this way ( I use ADT version: v21.0.0-531062 on Windows XP home edition)

<ol>
<li>Opened manifest file. </li>
<li>Changed the Existing project minSdkVersion to the same value as maxSdkVersion
( advise: it may be good to create a New project and see what is it's maxSdkVersion ) </li>
<li>Save manifest file.</li>
<li>Right Click the project and select Build Project.</li>
<li>From top menu: Project - Clean.. - check Only the relevant project, below I checked Start a build immediately and Build only the selected projects and OK.</li>
<li>open the java file - NO red errors anymore !</li>
<li>Back to step 1 above and changing Back minSdkVersion to it's Original value (to supoprt as many Android version as possible).</li>
</ol>

It worked BUT the problem returns every few days. I do the same as above and it solves and lets me develop.

blocks|key|273594|text|除了已经建议的缺少类文件的原因之外，此错误还可能指示重复的类文件，当构建路径上的类文件使用另一个在构建路径中具有多个定义的类时，eclipse会报告此错误。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|273595|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 addition to the already suggested cause of missing a class file this error can also indicate a duplicate class file, eclipse reports this error when an class file on the build path uses another class that has multiple definitions in the build path.

blocks|key|271710|text|由于您给了我们很少的细节，很可能是您所做的，这是一个非常容易犯的错误，而不是去|type|unstyled|depth|inlineStyleRanges|entityRanges|data|271711|Build+Path+>+Configure+Build+Path+>+Projects|offset|length|style|CODE|271712|并从那里添加额外的项目文件夹，而不是转到|271713|Build+Path+>+Configure+Build+Path+>+Libraries|271714|并从那里添加了您的项目文件夹。|271715|如果您的代码都是正确的，那么就是这种情况，但是在通过ctrl%2Bspace快捷方式自动重新组织导入时，您的引用都指向bin.com.your.additionalproject，而不是引用com.your.additionalproject的导入语句。|271716|注意垃圾桶。这意味着您通过将其他项目文件夹结构作为库来间接引用您的类，让您的IDE执行所有wokr来查找您所引用的确切的二进制类。|271717|要更正此问题，请从库中删除该文件夹，并将其添加到项目选项卡下，然后重新组织导入。你的项目应该工作得很好。|271718|entityMap^0|0|0|18|0|0|0|19|0|0|Q|A|0|0|0^^$0|@$1|2|3|4|5|6|7|V|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|W|8|@$D|X|E|Y|F|G]]|9|@]|A|$]]|$1|H|3|I|5|6|7|Z|8|@]|9|@]|A|$]]|$1|J|3|K|5|6|7|10|8|@$D|11|E|12|F|G]]|9|@]|A|$]]|$1|L|3|M|5|6|7|13|8|@]|9|@]|A|$]]|$1|N|3|O|5|6|7|14|8|@$D|15|E|16|F|G]]|9|@]|A|$]]|$1|P|3|Q|5|6|7|17|8|@]|9|@]|A|$]]|$1|R|3|S|5|6|7|18|8|@]|9|@]|A|$]]|$1|T|3|-4|5|6|7|19|8|@]|9|@]|A|$]]]|U|$]]

Since you give us very little details, most likely what you did, which is an incredibly easy mistake to make, is that instead of heading to 

<code>Build Path &gt; Configure Build Path &gt; Projects</code> 

and adding your additional project folder from there, instead you went to

<code>Build Path &gt; Configure Build Path &gt; Libraries</code> 

and added your project folder from there instead.

This is most definitely the case if your code is all correct, but upon automatically reorganizing imports via the <code>ctrl+space</code> shortcut , instead of your import statements referring to com.your.additionalproject, your references all point to bin.com.your.additionalproject. 

Note the bin. Meaning that you -are- indirectly referring to your class by treating your other project folder structure as a library, making your IDE doing all the wokr of finding the exactly binary class you're referring to.

To correct this, remove the folder from the Libraries, and instead add it under the Projects tab, and reorganize your imports. Your project should work fine.

blocks|key|271764|text|当我使用新的eclipse版本并尝试使用旧的eclipse版本所使用的以前的工作区时，出现了这个错误。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|271765|下面是我解决这个问题的方法：|271766|在Package+->+->+Build+Path+JRE+->上右键单击my+project，我在JRE上看到一个错误(十字)。因为找不到路径。->双击JRE系统库->选择选项"Workspace+Default+JRE“->+Finish+->+OK。->+BUM工作正常|271767|仅供参考。|271768|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|$]]

When i use a new eclipse version and try to use the previous workspace which i used with old eclipse version, this error occured.

Here is how i solve the problem:

Right click my project on Package Explorer -> Properties -> Java Build Path -> Libraries -> I see an error(Cross Sign) on JRE System Library. Because the path cannot be found. -> Double click the JRE System Library -> Select the option "Workspace Default JRE" -> Finish -> OK. -> BUM IT IS WORKING

FYI.

blocks|key|2976866|text|在我的例子中，这是因为我向pom.xml文件添加了一个新的依赖项。|type|unstyled|depth|inlineStyleRanges|offset|length|style|CODE|entityRanges|data|2976867|新的依赖关系依赖于旧版本的库(2.5)。我的pom.xml中的另一个库也需要这个库，但它需要3.0版。|2976868|由于某些原因，当Maven遇到这些冲突时，它会简单地忽略最新版本。在Eclipse中查看pom.xml时，您可以选择底部的"dependency+hierarchy“选项卡来查看依赖项是如何解析的。在这里，你会发现有问题的库(以及类)是否因为这个原因被省略了。|2976869|在我的例子中，它就像锁定新版本一样简单。您可以通过右键单击该条目来执行此操作-在上下文菜单中有一个将其锁定的选项。|2976870|entityMap^0|D|7|0|M|7|0|18|7|0|0^^$0|@$1|2|3|4|5|6|7|N|8|@$9|O|A|P|B|C]]|D|@]|E|$]]|$1|F|3|G|5|6|7|Q|8|@$9|R|A|S|B|C]]|D|@]|E|$]]|$1|H|3|I|5|6|7|T|8|@$9|U|A|V|B|C]]|D|@]|E|$]]|$1|J|3|K|5|6|7|W|8|@]|D|@]|E|$]]|$1|L|3|-4|5|6|7|X|8|@]|D|@]|E|$]]]|M|$]]

In my case it was a result of my adding a new dependency to my <code>pom.xml</code> file. 

The new dependency depended on an old version of a library (2.5). That same library was required by another library in my <code>pom.xml</code>, but it required version 3.0. 

For some reason, when Maven encounters these conflicts it simply omits the most recent version. In Eclipse when viewing <code>pom.xml</code> you can select the "dependency hierarchy" tab at the bottom to see how dependencies are resolved. Here you will find if the library (and thus class) in question has been omitted for this reason.

In my case it was as simple as locking down the newer version. You can do so by right-clicking the entry - there is an option to lock it down in the context menu.

blocks|key|2976937|text|将构建路径中的JRE指向JDK。这对我很管用。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|2976938|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|$]]

Point the JRE in the Build path to a JDK. That worked for me.

blocks|key|273789|text|对我来说，上面的解决方案都不起作用。对我来说起作用的是选择类中的所有代码，然后将其转换为注释，保存，然后将其转换回普通文本，错误就消失了。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|273790|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 none of the solutions above worked.
What worked for me was to select all the code in the class, then convert it to a comment,
save, then convert it back to normal text, the error was gone.

blocks|key|2977023|text|在我的例子中，当在Tomcat中启动web应用程序时，问题是"javax.ws.rs.webapplicationexception不能被解决“。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|2977024|添加以下库(Maven)的解决方案：|2977025|<dependency>
++++<groupId>javax.ws.rs</groupId>
++++<artifactId>javax.ws.rs-api</artifactId>
++++<version>2.0</version>
</dependency>|code-block|syntax|javascript|2977026|entityMap^0|0|0|0^^$0|@$1|2|3|4|5|6|7|K|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|L|8|@]|9|@]|A|$]]|$1|D|3|E|5|F|7|M|8|@]|9|@]|A|$G|H]]|$1|I|3|-4|5|6|7|N|8|@]|9|@]|A|$]]]|J|$]]

In my case the problem was &quot;javax.ws.rs.webapplicationexception cannot be resolved&quot; in execution when starting the web application in Tomcat.
Solution adding the following library (Maven):
<pre><code>&lt;dependency&gt;
 &lt;groupId&gt;javax.ws.rs&lt;/groupId&gt;
 &lt;artifactId&gt;javax.ws.rs-api&lt;/artifactId&gt;
 &lt;version&gt;2.0&lt;/version&gt;
&lt;/dependency&gt;
</code></pre>

I got an error in Eclipse. What does this error message means:

<blockquote>
 The type iglu.ir.TermVector cannot be resolved. It is indirectly referenced from required .class files
</blockquote>

Eclipse error: indirectly referenced from required .class files?

我在Eclipse中遇到一个错误。此错误消息意味着什么：无法解析类型iglu.ir.TermVector的。它是从必需的.class文件间接引用的

问Eclipse错误:从所需的.class文件间接引用？
EN

回答 21

Stack Overflow用户

Stack Overflow用户

Stack Overflow用户

社区

活动

资源

关于

腾讯云开发者

热门产品

热门推荐

更多推荐

问Eclipse错误:从所需的.class文件间接引用？EN

回答 21

Stack Overflow用户

Stack Overflow用户

Stack Overflow用户

社区

活动

资源

关于

腾讯云开发者

热门产品

热门推荐

更多推荐

问Eclipse错误:从所需的.class文件间接引用？
EN