Bug 551186 - Problem markers not removed for resolved build cycle
Summary: Problem markers not removed for resolved build cycle
Status: NEW
Alias: None
Product: JDT
Classification: Eclipse Project
Component: Core (show other bugs)
Version: 4.13   Edit
Hardware: PC Linux
: P3 normal (vote)
Target Milestone: ---   Edit
Assignee: JDT-Core-Inbox CLA
QA Contact:
URL:
Whiteboard: stalebug
Keywords: investigate
Depends on:
Blocks:
 
Reported: 2019-09-18 05:14 EDT by Lars Vogel CLA
Modified: 2024-03-09 15:20 EST (History)
4 users (show)

See Also:


Attachments
Example with three projects (4.90 KB, application/zip)
2019-09-18 05:14 EDT, Lars Vogel CLA
no flags Details
C doesnt depend on A (4.89 KB, application/zip)
2019-09-18 08:05 EDT, Vikas Chandra CLA
no flags Details

Note You need to log in before you can comment on or make changes to this bug.
Description Lars Vogel CLA 2019-09-18 05:14:38 EDT
Created attachment 279909 [details]
Example with three projects

I have a plug-in project A which depends on B which depends on C. And C depends on A. Eclipse correctly says:

Description	Resource	Path	Location	Type
A cycle was detected in the build path of project 'a'. The cycle consists of projects {a, b, c}	a		Build path	Build Path Problem
A cycle was detected in the build path of project 'b'. The cycle consists of projects {a, b, c}	b		Build path	Build Path Problem
A cycle was detected in the build path of project 'c'. The cycle consists of projects {a, b, c}	c		Build path	Build Path Problem
The project cannot be built until build path errors are resolved	a		Unknown	Java Problem
The project cannot be built until build path errors are resolved	b		Unknown	Java Problem
The project cannot be built until build path errors are resolved	c		Unknown	Java Problem


Now I remove the dependency in C to A. If I save I still have the following two messages:

Description	Resource	Path	Location	Type
The project cannot be built until its prerequisite b is built. Cleaning and building all projects is recommended	a		Unknown	Java Problem
The project cannot be built until its prerequisite c is built. Cleaning and building all projects is recommended	b		Unknown	Java Problem

Project Clean All is unable to solve that.

To reproduce: 
Import the three projects from the zip
Remove dependency in C to A
Save -> Two errors still remain
Project -> Clean -> Two errors still remain
Comment 1 Lars Vogel CLA 2019-09-18 05:16:48 EDT
Tested with Eclipse IDE for Java Developers
Version: 2019-06 (4.12.0)
Build id: 20190614-1200
OS: Linux, v.3.10.0-957.27.2.el7.x86_64, x86_64 / gtk 3.22.30, WebKit 2.20.5
Java version: 1.8.0_141
Comment 2 Vikas Chandra CLA 2019-09-18 08:03:25 EDT
Workaround: Closing and opening all the project solves the problem.

However the bug - comment#0 looks interesting.
Comment 3 Vikas Chandra CLA 2019-09-18 08:05:03 EDT
Created attachment 279910 [details]
C doesnt depend on A

Making C depend on A causes error ( as expected ) and removing C as depending gives 0 error.

My observation !

However the bug - comment#0 still remains !
Comment 4 Andrey Loskutov CLA 2019-09-18 10:33:50 EDT
*** Bug 551147 has been marked as a duplicate of this bug. ***
Comment 5 Andrey Loskutov CLA 2019-09-19 02:30:23 EDT
Why is this bug for PDE? The cycle error is coming from JDT?
Comment 6 Lars Vogel CLA 2019-09-19 02:31:53 EDT
(In reply to Andrey Loskutov from comment #5)
> Why is this bug for PDE? The cycle error is coming from JDT?

Please move it
Comment 7 Eclipse Genie CLA 2022-03-17 01:56: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.

If you have further information on the current state of the bug, please add it. 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.
Comment 8 Eclipse Genie CLA 2024-03-09 15:20:36 EST
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.

If you have further information on the current state of the bug, please add it. 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.