Created attachment 134555 [details]
Ant project test case in zip file

Product Version: NetBeans IDE 7.3 (Build 201302132200)
Java: 1.7.0_15; Java HotSpot(TM) Client VM 23.7-b01
Runtime: Java(TM) SE Runtime Environment 1.7.0_15-b03
System: Windows XP version 5.1 running on x86; Cp1252; en_NZ (nb)

I change the method signature of a method in an interface, then subsequently change the implementation to match. Classes using this method that did not have the calls changed to match are not flagged as erroneous.

Normally one would expect parsing errors to highlight the classes in red.

But here this fails for some strange reason.

Only if I open the classes that call the changed method in the editor, then the IDE starts scanning once more and the errors are detected.


How to reproduce:

- Open the attached project
- In the editor, open files Offer.java, SessionLocal.java, Session.java, no more
- In Offer.java, disable comment block 1 between "Alternate block  1 start" and "Alternate block  1 end" with "//"
- In Offer.java, enable uncomment block 2 between "Alternate block  2 start" and "Alternate block  2 end"
- Save Offer.java
- In SessionLocal.java, disable comment line with "// Alternate 1"
- In SessionLocal.java, enaable uncomment line with "// Alternate 2"
- Save SessionLocal.java
- In Session.java, disable comment block 1 between "Alternate block  1 start" and "Alternate block  1 end" with "//"
- In Session.java, enable uncomment block 2 between "Alternate block  2 start" and "Alternate block  2 end"
- Save Session.java
- Press [Ctrl+1] to switch to the Projects window and watch SessionTest.java

Expected behavior: The SessionTest.java tree node should have a red error icon.

Actual behavior: The SessionTest.java tree node has the normal icon

- Open SessionTest.java in the editor

In the editor, the line List<Offer> resultList = instance.getFavoriteOffers(memberId);
shows an error. After a while scanning starts, and in the Projects window, the SessionTest.java tree node changes to the red error icon.

This reproduces always on my computer, and I have seen this also with a different recent dev build.