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

Bug 350061

Summary: Warnings disappear on re-build if source file not changed
Product: [Tools] CDT Reporter: Michael Perkins <michael.perkins>
Component: cdt-buildAssignee: cdt-build-inbox <cdt-build-inbox>
Status: NEW --- QA Contact: Jonah Graham <jonah>
Severity: normal    
Priority: P3 CC: cdtdoug, yevshif
Version: 8.0   
Target Milestone: ---   
Hardware: PC   
OS: Windows XP   
Whiteboard:

Description Michael Perkins CLA 2011-06-22 10:24:36 EDT 
Build Identifier: I20110310-1119

If you build a project containing a file that gives warnings, the warnings are reported in the Problems tab. They also appear as tool tips in the source file. At this point, the Build icon is greyed-out. If you click now on the source file, without changing it, the Build icon is un-greyed. Now if you hit Build, the source file, not being changed, doesn't get rebuilt, but the Problems tab is repopulated, so all the warnings and tool tips disappear for the source file. 

It would be much nicer if the problems remained in the Problems tab when the source file is not rebuilt, as otherwise they come and go depending on which files are rebuilt each time.

Reproducible: Always

Steps to Reproduce:
1. Create a project and write a small C program that provokes a warning.
2. Build - you'll see warning in Problems tab.
3. Click in source code.
4. Click Build again - warning disappears from Problems tab.
Comment 1 Andrew Gvozdev CLA 2013-09-26 12:27:21 EDT 
A solution for this bug could be similar to the fix for bug 105978. It should be more elaborate to record the file being built as the origin/source of a marker rather than the project as done in bug 105978.