blocks|key|1701415|text|我有同样的问题，并随机地做了(几次)这样的事情：|type|unstyled|depth|inlineStyleRanges|entityRanges|data|1701416|1)项目->清理...，|1701417|2)重新关闭并打开Eclipse。|1701418|3)运行方式...|1701419|它又开始工作了，不需要改变配置。|1701420|entityMap^0|0|0|0|0|0^^$0|@$1|2|3|4|5|6|7|L|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|M|8|@]|9|@]|A|$]]|$1|D|3|E|5|6|7|N|8|@]|9|@]|A|$]]|$1|F|3|G|5|6|7|O|8|@]|9|@]|A|$]]|$1|H|3|I|5|6|7|P|8|@]|9|@]|A|$]]|$1|J|3|-4|5|6|7|Q|8|@]|9|@]|A|$]]]|K|$]]

I had same problem and randomly did such things as (several times): 

1) Project->Clean..., 
2) close and open Eclipse again, 
3) Run As...

And it started to work again, without changing configuration.

blocks|key|1701975|text|右键单击您的项目，然后转到Properties+>+Java+Build+Path+>+Source。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|1701976|确保您的源目录(例如MyProject/src)作为源文件夹列出。否则，您将不会得到任何红色标记。|1701977|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|$]]

Right-click your project and go to Properties > Java Build Path > Source.

Make sure your source directory (for example MyProject/src) is listed as a Source folder. Otherwise you won't get any red markers.

blocks|key|1701725|text|如果谷歌把你带到这个问题上，我想在这里发布我的故事。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|1701726|不知何故，“项目->自动构建”被关闭了。|1701727|将其重新打开会生成更正错误列表。|1701728|在我的例子中，它与m2e+1.0无关。这是任何Java项目的默认行为，可以追溯到Ganymede+(在撰写本文时，我正在运行Indigo+)|1701729|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 want to post my story here if Google brings you to this question.

Somehow, "Project->Build Automatically" got turned off.

Turning it back on produces correct errors list.

In my case it has nothing to do with m2e 1.0. This is default behavior for any Java project and goes back as far as Ganymede ( at the point of writing this post I am running Indigo )

blocks|key|1486784|text|我安装和卸载ajdt-plugin，得到同样的问题。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|1486785|检查<Project><Properties><Builders>。它应该有一个“Java+Builder”。|offset|length|style|CODE|1486786|这段代码应该在.project文件中(该文件位于项目的根目录中)：|1486787|<buildSpec>
++++++++<buildCommand>
++++++++++++++++<name>org.eclipse.jdt.core.javabuilder</name>
++++++++++++++++<arguments>
++++++++++++++++</arguments>
++++++++</buildCommand>
</buildSpec>
<natures>
++++++++<nature>org.eclipse.jdt.core.javanature</nature>
</natures>|code-block|syntax|javascript|1486788|entityMap^0|0|2|V|0|0|0^^$0|@$1|2|3|4|5|6|7|Q|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|R|8|@$D|S|E|T|F|G]]|9|@]|A|$]]|$1|H|3|I|5|6|7|U|8|@]|9|@]|A|$]]|$1|J|3|K|5|L|7|V|8|@]|9|@]|A|$M|N]]|$1|O|3|-4|5|6|7|W|8|@]|9|@]|A|$]]]|P|$]]

I installed and deinstalled ajdt-plugin and got the same problem.

Check <code>&lt;Project&gt;&lt;Properties&gt;&lt;Builders&gt;</code>.
It should have a 'Java Builder'.

This code should be in the .project file (file is in the root of your project):

<pre><code>&lt;buildSpec&gt;
 &lt;buildCommand&gt;
 &lt;name&gt;org.eclipse.jdt.core.javabuilder&lt;/name&gt;
 &lt;arguments&gt;
 &lt;/arguments&gt;
 &lt;/buildCommand&gt;
&lt;/buildSpec&gt;
&lt;natures&gt;
 &lt;nature&gt;org.eclipse.jdt.core.javanature&lt;/nature&gt;
&lt;/natures&gt;
</code></pre>

blocks|key|1486740|text|我今天也遇到了这个问题。这里介绍的其他解决方案(例如清理项目和重新启动Eclipse)不起作用，或者不适用于我的设置。对我来说起作用的是右键单击Package+Explorer中的项目并选择Maven->Update+project+Configuration。显然，我前一天所做的一些源文件夹重构导致Maven失去了对事物的跟踪，并发出此命令修复了一切。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|1486741|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 was experiencing this problem as well today. The other solutions presented here (such as cleaning the project and restarting Eclipse) did not work or were not applicable to my setup. What did work for me was right-clicking on the project in the Package Explorer and selecting Maven->Update Project Configuration. Evidently some source folder restructuring I had done the previous day had caused Maven to lose track of things, and issuing this command fixed everything.

blocks|key|1701383|text|在problems窗口的右上角(最小化旁边)有一个小箭头图标。单击它并选择"Configure+filters“。可能已激活了严重性筛选器。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|1701384|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|$]]

At the top right corner of the problems window (next to minimize) there is a small arrow-icon. Click it and select "Configure filters". There is a severity filter that might have been activated.

blocks|key|1701586|text|我在略有不同的情况下也有同样的问题。我有一个父POM和下面的多个模块。项目已经存在，我将其导入到eclipse中。我只能将“依赖管理”更改为父项目，而不能更改其下的项目。它们没有显示任何编译警告。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|1701587|接下来，我将尝试将它们全部更改为单独的项目……这不是我想要的，但我一直无法解决这个问题...|1701588|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|$]]

I have the same problem in slight different situation. I have a parent POM and multiple modules under it. Project was existing and I imported it into eclipse. I can change the "Dependency management" only to parent project but not projects under it. They are not showing any compilation warnings. 

Next I'm going to try to change them all into individual projects... that's not what I wanted, but I haven't been able to solve this otherwise...

blocks|key|1486472|text|我也遇到过同样的问题。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|1486473|安装Java后，我没有收到任何m2eclipse编译错误。|1486474|我的解决方案是通过选择项目->右键单击(进入上下文菜单)+->+m2+Maven+->启用依赖项管理来启用依赖项管理。|1486475|现在我可以查看Java编译错误了。|1486476|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 have also faced the same problem.

After installing m2eclipse plugin, i was not getting any Java compilation errors. 

My solution was to enable dependency management by Select Project -> Right Click (to get context menu) -> m2 Maven -> Enable dependency management. 

Now i am able to view Java Compilation Errors.

blocks|key|1486275|text|在Ganymede上，检查Problem视图的配置：|type|unstyled|depth|inlineStyleRanges|entityRanges|data|1486276|('Configure+content')它可以在‘同一项目中的任何元素’上设置，并且您当前可以从项目中选择一个元素。|1486277|或者它可能是在工作集上设置的，并且此工作集已被修改|1486278|确保选择了“匹配任何配置”。|1486279|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|$]]

On Ganymede, check the configuration of the Problem view:

('Configure content') It can be set on 'any element in the same project' and you might currently select an element from the project.

Or it might be set on a working set, and this working set has been modified

Make sure that 'Match any configuration' is selected.

blocks|key|1486817|text|在我的例子中，Eclipse没有正确地选取当前项目所依赖的Java项目。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|1486818|您可以转到“项目”>“BuildPath”>“配置BuildPath”，然后删除并重新添加项目。|1486819|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|$]]

In my case Eclipse wasn't properly picking up a Java project that a current project was dependent on. 

You can go to Project > BuildPath > Configure BuildPath and then delete and re-add the project.

blocks|key|1487020|text|显然有几个原因可能会发生这种情况，我想我应该为我的问题添加解决方案。(我有一个java项目，其中导入了带有虚拟链接的文件)|type|unstyled|depth|inlineStyleRanges|entityRanges|data|1487021|如果你有像我这样的情况，你会有另一个文件夹与你的'src‘文件夹处于同一级别。如果是，请右键单击其他文件夹，然后选择“Build+Path”>“Add+to+Build+Path”(如果您看到“Build+Path”>“Remove+from+Build+Path”，则它已经被添加。)|1487022|要进一步配置构建路径，请右键单击顶级项目目录，然后选择“构建路径”>“配置构建路径”。您的文件夹应显示在“源”选项卡中。|1487023|要配置您看到的错误，请单击Java+Compiler+>+errors+/Warning，然后单击'Configure+Workspace+Settings‘。这与进入Window+>+Preferences+>+Java+>+Compiler+>Errors/Warning相同。如果您不希望Eclipse忽略某些内容，那么只需将其更改为Warning即可。|1487024|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|$]]

There are obviously several reasons why this might occur, and I thought I'd add the solution to my issue. (I have a java project into which I have imported files with virtual links)

If you have a situation like mine, you will have another folder on the same level as your 'src' folder. If you do, right-click on that other folder, then select 'Build Path' > 'Add to Build Path' (if you see 'Build Path' > 'Remove from Build Path', then it had already been added.)

To further configure the Build Path, right click on your top level project dir, and select 'Build Path' > 'Configure Build Path'. Your folders should show up in the 'Source' tab.

To configure what errors you see, Click on Java Compiler > Errors/Warnings and then click 'Configure Workspace Settings'. That is the same as going to Window > Preferences > Java > Compiler > Errors/Warnings. If you don't want Eclipse to ignore something, then just change it to Warning.

blocks|key|1702435|text|如果你已经到了这里，那就意味着所有其他的解决方案对你都不起作用。一个原因可能是你的源文件夹不是java项目。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|1702436|解决方案是在源文件夹上运行下面的命令|1702437|mvn+eclipse:eclipse|code-block|syntax|javascript|1702438|这对我很有效。|1702439|如果同样不起作用，请尝试删除.classpath和.project文件，然后再次运行上述命令|1702440|entityMap^0|0|0|0|0|0^^$0|@$1|2|3|4|5|6|7|O|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|P|8|@]|9|@]|A|$]]|$1|D|3|E|5|F|7|Q|8|@]|9|@]|A|$G|H]]|$1|I|3|J|5|6|7|R|8|@]|9|@]|A|$]]|$1|K|3|L|5|6|7|S|8|@]|9|@]|A|$]]|$1|M|3|-4|5|6|7|T|8|@]|9|@]|A|$]]]|N|$]]

If you have reached here that means all the other solutions did not work for you.
One reason could be your source folder is not a java project.

Solution would be to run below command on the source folder

<pre><code>mvn eclipse:eclipse
</code></pre>

This worked for me. 

If this also doesn't work then try removing .classpath and .project file and run the above command again

blocks|key|1487405|text|这是正常的问题。按顺序和导出功能有时会被关闭。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|1487406|右键单击project|1487407|1487408|entityMap^0|0|0|0^^$0|@$1|2|3|4|5|6|7|G|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|H|8|@]|9|@]|A|$]]|$1|D|3|-4|5|6|7|I|8|@]|9|@]|A|$]]|$1|E|3|-4|5|6|7|J|8|@]|9|@]|A|$]]]|F|$]]

This is normal problem. In wich order and export function sometimes get turned off.
right click on project&lt;properties&lt; there u hav option
build path &lt; and there ORDER AND EXPORT&lt; click right all the options....all the things are right back.

blocks|key|1702575|text|对我来说起作用的是创建一个New+Problems+View+(这个选项可以从三点视图选项中访问)：|type|unstyled|depth|inlineStyleRanges|offset|length|style|CODE|entityRanges|data|1702576|​|1702577|📷|atomic|1702578|1702579|新视图会显示检测到的所有警告和错误：|1702580|1702581|1702582|1702583|entityMap|0|IMAGE|mutability|IMMUTABLE|imageUrl|https://ask.qcloudimg.com/http-save/yehe-900000/4ad0fe8e9be7a8f69d58e4b589b48c28.png|imageAlt|1|https://ask.qcloudimg.com/http-save/yehe-900000/2718203d4f20b1f7c515a2ad008ab274.png^0|D|H|0|0|0|1|0|0|0|0|0|0|1|1|0|0^^$0|@$1|2|3|4|5|6|7|11|8|@$9|12|A|13|B|C]]|D|@]|E|$]]|$1|F|3|G|5|6|7|14|8|@]|D|@]|E|$]]|$1|H|3|I|5|J|7|15|8|@]|D|@$9|16|A|17|1|18]]|E|$]]|$1|K|3|G|5|6|7|19|8|@]|D|@]|E|$]]|$1|L|3|M|5|6|7|1A|8|@]|D|@]|E|$]]|$1|N|3|G|5|6|7|1B|8|@]|D|@]|E|$]]|$1|O|3|I|5|J|7|1C|8|@]|D|@$9|1D|A|1E|1|1F]]|E|$]]|$1|P|3|G|5|6|7|1G|8|@]|D|@]|E|$]]|$1|Q|3|-4|5|6|7|1H|8|@]|D|@]|E|$]]]|R|$S|$5|T|U|V|E|$W|X|Y|-4]]|Z|$5|T|U|V|E|$W|10|Y|-4]]]]

What worked for me is creating a <code>New Problems View</code> (this option is accessible from the three-dots View options):
<a href="https://i.stack.imgur.com/aUzLD.png" rel="nofollow noreferrer"><img src="https://i.stack.imgur.com/aUzLD.png" alt="screenshot showing 'New Problems View' option" /></a>
The new View does show all the warnings and errors that were detected:
<a href="https://i.stack.imgur.com/vIqGe.png" rel="nofollow noreferrer"><img src="https://i.stack.imgur.com/vIqGe.png" alt="enter image description here" /></a>

blocks|key|1701470|text|我可以通过创建一个带有非静态成员类的枚举和一个枚举其值的静态块来重现这个问题：|type|unstyled|depth|inlineStyleRanges|entityRanges|data|1701471|public+enum+Foo+{
Dummy(new+Bar+[]+{new+Bar()});
static+{
++++for+(Foo+foo:+Foo.values());
}
private+Foo(Bar+[]+params)+{}
public+class+Bar+{}
+}|code-block|syntax|javascript|1701472|这个类破坏了Ganymede编译器。如果删除静态初始值设定项块中的行，代码将再次正确编译，并且如预期的那样得到错误消息，即没有新的Bar()调用的封闭实例。|1701473|--更正:仅当项目具有来自Google+Appengine的gaeNature时，上述情况才成立。但是，如果您得到一个类似于原始问题中提到的错误，您可能会遇到另一个java编译器错误...|1701474|entityMap^0|0|0|0|0^^$0|@$1|2|3|4|5|6|7|M|8|@]|9|@]|A|$]]|$1|B|3|C|5|D|7|N|8|@]|9|@]|A|$E|F]]|$1|G|3|H|5|6|7|O|8|@]|9|@]|A|$]]|$1|I|3|J|5|6|7|P|8|@]|9|@]|A|$]]|$1|K|3|-4|5|6|7|Q|8|@]|9|@]|A|$]]]|L|$]]

I could reproduce this issue by creating an enumeration with a non-static member class and a static block enumerating its values:

<pre><code>public enum Foo {
Dummy(new Bar [] {new Bar()});
static {
 for (Foo foo: Foo.values());
}
private Foo(Bar [] params) {}
public class Bar {}
 }
</code></pre>

This class breaks the Ganymede compiler. If you delete the line in the static initializer block, the code compiles correctly again, and you get the error that there is no enclosing instance for the new Bar() call, as expected.

-- correction: The above holds only if the project has gaeNature from Google Appengine. However, if you get an error similar as mentioned in the original question, you might be encountering another java compiler bug ...

blocks|key|1701657|text|我在Eclipse+Helios和m2eclipse插件上也遇到了同样的问题。他们似乎不能让这个东西与WTP或WPT或任何该死的首字母缩写一起工作。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|1701658|如果我对项目进行清理并查看Maven控制台，那么我可以在控制台中看到编译问题，但eclipse不会接触到它。似乎eclipse或WTP/WPT和m2eclipse都在忙着拍手。|1701659|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|$]]

I have the same issue with Eclipse Helios and the m2eclipse plugin. They just can't seem to get this thing to work with WTP or WPT or whatever the blasted acronym is. 

If I do a clean on the project and watch the Maven console then I can see the compilation issues in the console but eclipse won't touch it. It seems eclipse or WTP/WPT and m2eclipse are busy playing slap hands.

blocks|key|1487154|text|我们使用SP2而不是Maven|type|unstyled|depth|inlineStyleRanges|entityRanges|data|1487155|上面的方法都没有帮助，我解决问题的方法是选择我的项目(r-Click)+>+Gradle+>+Refresh+All|1487156|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|$]]

Kepler SP2, Java Project (Web Driver), and we use Gradle instead of Maven

None of the above helped, what did fix the problem for me was to select my projects (r-Click) > Gradle > Refresh All

blocks|key|1487205|text|将源(Src)文件夹指向构建路径将很容易解决此问题。右键单击项目>构建路径>配置构建路径>+java构建路径>源>添加文件夹，然后单击应用|type|unstyled|depth|inlineStyleRanges|entityRanges|data|1487206|​|1487207|📷|atomic|offset|length|1487208|1487209|entityMap|0|IMAGE|mutability|IMMUTABLE|imageUrl|https://ask.qcloudimg.com/http-save/yehe-900000/0e111ea925b8f73f6534601fcefe512e.png|imageAlt^0|0|0|0|1|0|0|0^^$0|@$1|2|3|4|5|6|7|S|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|T|8|@]|9|@]|A|$]]|$1|D|3|E|5|F|7|U|8|@]|9|@$G|V|H|W|1|X]]|A|$]]|$1|I|3|C|5|6|7|Y|8|@]|9|@]|A|$]]|$1|J|3|-4|5|6|7|Z|8|@]|9|@]|A|$]]]|K|$L|$5|M|N|O|A|$P|Q|R|-4]]]]

Pointing the source(src) folder to the build path will solve this easily 
to do so
right click on the project > build path > configure build path > java build path > source > add folder and click Apply 

<a href="https://i.stack.imgur.com/smyFy.png" rel="nofollow noreferrer"><img src="https://i.stack.imgur.com/smyFy.png" alt="enter image description here"></a>

blocks|key|1702311|text|我的错误是我在资源包中创建类...|type|unstyled|depth|inlineStyleRanges|entityRanges|data|1702312|在src/main/java中创建类解决了这个问题。|1702313|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|$]]

My mistake was that I was creating classes in resource package...

Creating classes in src/main/java solved the issue.

blocks|key|1487318|text|检查您的筛选器，有时问题视图的范围可能是您当前未在其中工作的工作集。此外，您还可以检查problem视图的其他配置。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|1487319|​|1487320|📷|atomic|offset|length|1487321|1487322|entityMap|0|IMAGE|mutability|IMMUTABLE|imageUrl|https://ask.qcloudimg.com/http-save/yehe-900000/a1610bacad8e7e8043028e3e5efcc9bb.png|imageAlt^0|0|0|0|1|0|0|0^^$0|@$1|2|3|4|5|6|7|S|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|T|8|@]|9|@]|A|$]]|$1|D|3|E|5|F|7|U|8|@]|9|@$G|V|H|W|1|X]]|A|$]]|$1|I|3|C|5|6|7|Y|8|@]|9|@]|A|$]]|$1|J|3|-4|5|6|7|Z|8|@]|9|@]|A|$]]]|K|$L|$5|M|N|O|A|$P|Q|R|-4]]]]

Check your filters, sometimes problem view could be scoped to a working set that you are not currently working in. Also, you can check other configurations for the problem view.

<a href="https://i.stack.imgur.com/fvK8v.png" rel="nofollow noreferrer"><img src="https://i.stack.imgur.com/fvK8v.png" alt="enter image description here"></a>

blocks|key|1702638|text|.classpath中的问题我做了“替换为HEAD版本”，以找回我在仓库Git中的版本，错误再次出现。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|1702639|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|$]]

Problem in .classpath
I did &quot;Replace with HEAD revision&quot; to get back the version that I had in the repository Git and the errors appear again.

blocks|key|1702177|text|在我的例子中，我设置了一个旧的工作空间，这就是问题所在。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|1702178|尝试为工作区设置新文件夹|1702179|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|$]]

In my case I setted a old workspace and it was the problem.

Try to set a new folder for workspace

blocks|key|1487077|text|如果"Debug“最近已被激活，则选中程序的右上角(在最小化按钮下)，然后单击back+of。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|1487078|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 "Debug" has been recently activated then check the top right of the program (under the Minimise button) and click back onto Java.

For some reason Eclipse is no longer showing me Java compilation Errors in the Problems View.

It is still showing Warnings.

This has suddenly happened and I cannot think of anything that I have changed which would affect this.

I am using the "Maven Integration for Eclipse" plugin but I have been for some time - not sure if this could have affected it or not.

Any ideas?

Eclipse Problems View not showing Errors anymore

编译器

Eclipse

Java

由于某些原因，Eclipse不再在Problems视图中显示Java编译错误。它仍然显示警告。这是突然发生的，我想不出我有什么改变会影响到这一点。我正在使用"Maven Integration for Eclipse“插件，但我已经使用了一段时间--不确定这是否会影响它。有什么想法吗？

问Eclipse问题视图不再显示错误
EN

回答 23

Stack Overflow用户

Stack Overflow用户

Stack Overflow用户

社区

活动

资源

关于

腾讯云开发者

热门产品

热门推荐

更多推荐

问Eclipse问题视图不再显示错误EN

回答 23

Stack Overflow用户

Stack Overflow用户

Stack Overflow用户

社区

活动

资源

关于

腾讯云开发者

热门产品

热门推荐

更多推荐

问Eclipse问题视图不再显示错误
EN