Bug 579690 - Project explorer does not show compilations errors in Eclipse 2022-03 on WAR projects
Summary: Project explorer does not show compilations errors in Eclipse 2022-03 on WAR ...
Status: CLOSED WONTFIX
Alias: None
Product: e4
Classification: Eclipse Project
Component: UI (show other bugs)
Version: unspecified   Edit
Hardware: PC Windows 11
: P3 normal with 2 votes (vote)
Target Milestone: ---   Edit
Assignee: Project Inbox CLA
QA Contact:
URL:
Whiteboard: stalebug
Keywords:
Depends on:
Blocks:
 
Reported: 2022-04-13 18:30 EDT by Lucas de Carvalho Lopes CLA
Modified: 2024-05-15 05:31 EDT (History)
3 users (show)

See Also:


Attachments
Missing red X (101.85 KB, image/png)
2022-04-13 18:30 EDT, Lucas de Carvalho Lopes CLA
no flags Details
log file from test workspace (12.10 KB, text/plain)
2022-04-14 13:25 EDT, Lucas de Carvalho Lopes CLA
no flags Details

Note You need to log in before you can comment on or make changes to this bug.
Description Lucas de Carvalho Lopes CLA 2022-04-13 18:30:51 EDT
Created attachment 288440 [details]
Missing red X

After updating to Eclipse 2022-03 no projects will show compilations errors on the src/main/java in project explorer. I can only see the errors on "Makers" -> "Java problems" or navigating manually in the project's folders. 

In the attached print screen the "Usuario" class has an obvious error. But the class is not marked with an error on the upper arrow. It should, it was in the previous eclipse versions

The problem is not present on JAR projects. But it is on all my projects that have WAR packaging . Also happens on new projects

Obs: I could not figure it out how to report a bug in JDT product, this option doesn`t shows up for me, so I'm posting in this e4 product.
Comment 1 Wim Jongman CLA 2022-04-14 03:51:48 EDT
(In reply to Lucas de Carvalho Lopes from comment #0)

It looks like the project information is not loaded correctly.

Please try to close and then open the project.

Also, you can take a look at the decorators in the preferences to see if some of them were automatically disabled (this happens when an error occurs in the decorator)

Pref -> General -> Appearance -> Label decorations

Also, you can try a full rebuild Project -> Clean... -> all projects
Comment 2 Wim Jongman CLA 2022-04-14 03:54:31 EDT
(In reply to Lucas de Carvalho Lopes from comment #0)

> 
> Obs: I could not figure it out how to report a bug in JDT product, this
> option doesn`t shows up for me, so I'm posting in this e4 product.

The project has moved to GitHub: https://github.com/eclipse-jdt/
Comment 3 Lucas de Carvalho Lopes CLA 2022-04-14 12:36:18 EDT
(In reply to Wim Jongman from comment #1)
> (In reply to Lucas de Carvalho Lopes from comment #0)
> 
> It looks like the project information is not loaded correctly.
> 
> Please try to close and then open the project.
> 
> Also, you can take a look at the decorators in the preferences to see if
> some of them were automatically disabled (this happens when an error occurs
> in the decorator)
> 
> Pref -> General -> Appearance -> Label decorations
> 
> Also, you can try a full rebuild Project -> Clean... -> all projects

Hello!

Tried all of that, but did not solve the problem.

If I create a new empty project it works as expected. But as soon as I add the <packaging>war</packaging> on the POM file the problem I described shows up.
Comment 4 Wim Jongman CLA 2022-04-14 13:07:55 EDT
(In reply to Lucas de Carvalho Lopes from comment #3)

> 
> If I create a new empty project it works as expected. But as soon as I add
> the <packaging>war</packaging> on the POM file the problem I described shows
> up.

Is there anything in the error log?
Comment 5 Mickael Istria CLA 2022-04-14 13:20:58 EDT
I think this is a duplicate of bug 579170
Comment 6 Lucas de Carvalho Lopes CLA 2022-04-14 13:25:39 EDT
Created attachment 288447 [details]
log file from test workspace
Comment 7 Lucas de Carvalho Lopes CLA 2022-04-14 13:26:18 EDT
(In reply to Wim Jongman from comment #4)
> (In reply to Lucas de Carvalho Lopes from comment #3)
> 
> > 
> > If I create a new empty project it works as expected. But as soon as I add
> > the <packaging>war</packaging> on the POM file the problem I described shows
> > up.
> 
> Is there anything in the error log?

Nothing that seems related to that problem.
I created a new workspace and a new project in that workspace to see if something shows up in the log. The problem is present and the log file does not seem to point to anything related. I attached the log here, I may be missing something.
Comment 8 Alexander Rotnov CLA 2022-05-23 07:27:17 EDT
(In reply to Lucas de Carvalho Lopes from comment #7)
> (In reply to Wim Jongman from comment #4)
> > (In reply to Lucas de Carvalho Lopes from comment #3)
> > 
> > > 
> > > If I create a new empty project it works as expected. But as soon as I add
> > > the <packaging>war</packaging> on the POM file the problem I described shows
> > > up.
> > 
> > Is there anything in the error log?
> 
> Nothing that seems related to that problem.
> I created a new workspace and a new project in that workspace to see if
> something shows up in the log. The problem is present and the log file does
> not seem to point to anything related. I attached the log here, I may be
> missing something.

Try to delete project from workspace, then delete any Eclipse related project files (like .settings folder, .classpath and .project files and etc), and import project again (as Maven Project).
It seems to be an upgrate problem from older version.
Comment 9 Alexander Rotnov CLA 2022-05-25 17:48:48 EDT
Upd: Its not an upgrade problem. Problem reproduced on any new projects with WST related project natures (like Web Dynamic Project or Utility Module).
Comment 10 Eclipse Genie CLA 2024-05-15 05:31:39 EDT
This bug hasn't had any activity in quite some time. Maybe the problem got resolved, was a duplicate of something else, or became less pressing for some reason - or maybe it's still relevant but just hasn't been looked at yet. As such, we're closing this bug.

If you have further information on the current state of the bug, please add it and reopen this bug. The information can be, for example, that the problem still occurs, that you still want the feature, that more information is needed, or that the bug is (for whatever reason) no longer relevant.

--
The automated Eclipse Genie.