Some Eclipse Foundation services are deprecated, or will be soon. Please ensure you've read this important communication.

Bug 352635

Summary:	Eclipse Problems View not showing Errors anymore
Product:	z_Archived	Reporter:	Alex Pogrebnyak <alex-pub.eclipse>
Component:	m2e	Assignee:	Project Inbox <m2e.core-inbox>
Status:	CLOSED INVALID	QA Contact:
Severity:	normal
Priority:	P3	CC:	igor, xerces9
Version:	unspecified
Target Milestone:	---
Hardware:	PC
OS:	Windows XP
Whiteboard:

Description Alex Pogrebnyak

2011-07-20 14:07:30 EDT

This is a verbatim from this question on StackOverflow: http://stackoverflow.com/questions/253357/eclipse-problems-view-not-showing-errors-anymore

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

BTW, Tasks window is also empty.

This answer ( http://stackoverflow.com/questions/253357/eclipse-problems-view-not-showing-errors-anymore/411663#411663 ) is the only solution that restores the original functionality.

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

I think the step #3 is what makes it work again (Run As ...).

Note that original question describes problem with original m2eclipse plugin from Sonatype, but m2e 1.0 still exhibits the same problem.

Eclipse Java EE IDE for Web Developers.

Version: Indigo Release
Build id: 20110615-0604

  Embedded Maven Runtime 3.0.3	1.0.1.201106291304	org.sonatype.m2e.maven.runtime.3.0.3.feature.group	SONATYPE
  m2e - Maven Integration for Eclipse	1.0.0.201106052308	org.eclipse.m2e.feature.feature.group	Eclipse.org - m2e
  m2e - slf4j over logback logging (Optional)	1.0.0.201106052308	org.eclipse.m2e.logback.feature.feature.group	Eclipse.org - m2e
  m2e connector for antlr	0.13.0.20110622-1538	org.sonatype.m2e.antlr.feature.feature.group	Sonatype, Inc.
  m2e connector for build-helper-maven-plugin	0.13.0.20110622-1538	org.sonatype.m2e.buildhelper.feature.feature.group	Sonatype, Inc.
  m2e connector for modello	0.13.0.20110622-1538	org.sonatype.m2e.modello.feature.feature.group	Sonatype, Inc.
  Maven Integration for WTP (Optional)	0.13.0.20110623-0455	org.maven.ide.eclipse.wtp.feature.feature.group	Sonatype, Inc.
  Maven SCM Handler for CVS	0.13.0.201106260822	org.sonatype.m2e.cvs.feature.feature.group	Sonatype, Inc.
  Maven SCM Handler for EGit	0.13.0.20110628-2018	org.sonatype.m2e.egit.feature.feature.group	Sonatype, Inc.
  Maven SCM Handler for Subversive	0.13.0.201106211115	org.sonatype.m2e.subversive.feature.feature.group	Sonatype, Inc.
  Plexus Metadata Generation	0.13.0.20110622-1538	org.sonatype.m2e.plexus.annotations.feature.feature.group	Sonatype, Inc.
  ProjectSet	3.0.0.200905051715	com.csc.dip.projectset.feature.group	CSC Technologies Deutschland GmbH
  Subclipse (Required)	1.6.18	org.tigris.subversion.subclipse.feature.group	tigris.org
  Subversion Revision Graph	1.0.9	org.tigris.subversion.subclipse.graph.feature.feature.group	tigris.org
  Workspace Mechanic	0.0.9	com.google.eclipse.mechanic.feature.group	Google, Inc.

Comment 1 Igor Fedorenko

2011-07-21 01:54:22 EDT

Out of curiosity, why do you think this has anything to do with m2e? In any case, this bugreport will be closed as INVALID unless we get more information (details about how to reproduce the problem, relevant logs, patches that fix the problem, etc).

Comment 2 Alex Pogrebnyak

2011-07-21 06:48:17 EDT

(In reply to comment #1)
> Out of curiosity, why do you think this has anything to do with m2e? In any
> case, this bugreport will be closed as INVALID unless we get more information
> (details about how to reproduce the problem, relevant logs, patches that fix
> the problem, etc).

1. Because it was reported against m2eclipse more than 2 years ago ( StackOverflow question ).
2. I see '7/20/11 4:28:44 PM EDT: [ERROR] Error checking for warnings' log messages in m2e console.

I am willing to do the leg work (do debug logging, etc. ), but I need direction about what to do.

Comment 3 Igor Fedorenko

2011-07-21 08:35:48 EDT

I have no advice here, you'll have to work on this yourself. For the record, m2e does not directly work with problems view in any way, so I'd be really really surprised if the problem had anything to do with it.

Comment 4 Alex Pogrebnyak

2011-07-22 12:09:50 EDT

Closing as user error.

"Project->Build Automatically" somehow got turned off, and you need it ON in order to update errors list.

It's strange that when you type illegal code, the markers in file do get updated immediately, but error view does not.  But this is the behavior that goes back to Ganymede and is the same for any POJP ( Plain Old Java Project ) when no m2e is involved.

Sorry for the false alarm.

Comment 5 David Balažic

2019-11-05 06:17:18 EST

This just happened for me and a coworker, using:

Eclipse IDE for Enterprise Java Developers.

Version: 2019-03 (4.11.0)
Build id: 20190314-1200

After a few minutes the "Java Problems" group reappeared in the Markers tab.

What I did was:
 - clean project
 - remove a breakpoint (one breakpoint was listed in the Markers tab)
 - press F5 in Markers, as it did not react immediately to the deletion of the breakpoint (it was still showing it)


So:
 - the problem still exists
 - happens to several people (look for example at the original stackexchange question, it was a lot of traffic)

Also note: I had this problem in the Markers view, while the original report is about the Problems view. I suspect they have a common backend.

Comment 6 Denis Roy

2021-04-19 13:25:59 EDT

Moved to https://github.com/eclipse-m2e/m2e-core/issues/