Community
Participate
Working Groups
R3.4. Build path problems are not recreated with clean + full build. Noticed while testing the fix for bug 287164 but also happens with existing build path problems. 1. start new workspace 2. create Java project 'A' and 'B' 3. add 'A' to the build path of 'B' 4. add 'B' to the build path of 'A' ==> cycles are reported 5. delete all markers from the 'Problems' view 6. do a clean + full build ==> markers don't come back
I think the markers don't come back because building A depends on building B and vice versa. So in this scenario, the build doesn't complete and we bail out of a loop. I do see a new marker for both projects: The project cannot be built until its prerequisite B is built. Cleaning and building all projects is recommended
See bug 287164 comment 60
(In reply to comment #2) > See bug 287164 comment 60 Dani, Per rationale above, it would appear this is intentional per design. I would close this as such - do you disagree ?
(In reply to comment #3) > (In reply to comment #2) > > See bug 287164 comment 60 > > Dani, Per rationale above, it would appear this is intentional per design. That design was OK back in the old days. Unfortunately, one can delete markers from the Problems view these days. Therefore we also need to have a way to bring those back. In addition, those markers are really build related markers and since 'Clean' states: "Clean will discard all build problems and built states.", we should also remove those markers when cleaning to have a consistent story. We don't have to fix this bug right now, but keep it open with low priority.
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.
This is still a bad bug that can be reproduced in 4.11 RC1. The bad part about this is that the user - does not get the red ! on the projects ==> does not know/expect a build path problem - there is no error reported for the cycles ==> the user has no means to fix the probem
