Bug 322720

Description Daniel Alvarez Arribas 2010-08-15 09:35:47 EDT

Build Identifier: 20100617-1415

If have created a project with a source tree that's multiple levels deep.

There are several syntax errors in various PHP source files.

The PHP Explorer view correctly marks the top-level project directory, each of the source files that contain syntax errors, and the directories directly containing those files with a red 'x' icon.

The intermediate directories (3rd level, 4th level etc, down to the directory directly containing the file) are sometimes, BUT NOT ALWAYS, marked with a red 'x' icon.

This means that after clicking through all 2nd-level directories that have been marked, there are still syntax errors remaining, and from the PHP Explorer view there's no way to tell which subdirectories contain the remaining broken source files - you have to click through each of the directories or use a different view.

You can reduce this to a scenario where there is a single source file with syntax errors, and all the 3rd- and 4th-level directories containing that file are not marked.

I think the 'x'-ing feature is supposed to work differently (correctly marking all levels) and is broken. 


I tried refreshing the view, validating the view and each of the directories,
and manually rebuilding (Build all), but it did not change the marking.


Something that might be relevant: I imported a source tree into the project by copying files into the workspace and adding the source directory under "Project -> Properties -> PHP Build path".

Reproducible: Always

Steps to Reproduce:
1. Take any source tree with various levels of subdirectories (in my example there are four levels of directories below the top-level project directory. That's five levels including the top-level project directory)
2. Willingly cripple the code at random places to contain syntax errors
3. Watch the effect on the red x'es in the tree in the Project Explorer View
   At least some of the 3rd- and 4th-level directories containing errors will 
   not have been marked correctly.
4. Rebuild, refresh, revalidate - whatever. It won't help.