This Bugzilla instance is a read-only archive of historic NetBeans bug reports. To report a bug in NetBeans please follow the project's instructions for reporting issues.
Hi, in my java application project, test file tree in project explorer pane doesn't show any compilation error mark even thought files are not correct. I noticed that if I open an incorrect file in java editor, make some changes (like adding blank spaces) and save it the red mark appears as expected on changed file. Is this a known behaviour? PS: I have only one project open at a time. Thanks for help Filippo Mariotti OS: Linux Fedora 9 (2.6.26.5-45.fc9.i686.PAE) Java: build 1.6.0_07-b06 Netbeans: Dev 200810171401
I cannot reproduce in the following config: Product Version: NetBeans IDE Dev (Build 200810171401) Java: 1.5.0_16; Java HotSpot(TM) Client VM 1.5.0_16-133 System: Mac OS X version 10.5.5 running on i386; MacRoman; en_US (nb) Could you please provide steps to reproduce (if it is 100% reproducible) and also attach screenshot. Thanks.
Sure, I created a simple project. You can find attached here. Open with NB, and compile everything (shift-F11 and F9). It should be fine. Now replace public boolean MyMethod(String message) { // do something message.substring(0); return true; } in MyClass.java with public int MyMethod(String message) { // do something message.substring(0); return 0; } As expected if you save all and execute F9 to build the tests it should give you an error. After doing that the situation in my IDE is like the screenshot attached. I should see the red mark on MyClassTest.java in the project explorer pane. But it appear only after I change and save MyClassTest.java file. Let me know if you need more info and thanks for your time. Regards Filippo Mariotti
Created attachment 72302 [details] Test Project
Created attachment 72303 [details] Screenshot
Maybe duplicate of issue 147000
May be, but in this case waiting is not a solution. Even after a long time the error mark doesn't appear. It require a new Save to refresh the file status. Filippo
Any news? regards Filippo Mariotti
Overtake.
the problem is not same as issue #147000 but similar.
Adding into umbrella issue.
Resolving all issues with milestone "future" as LATER. If you feel strongly that it should be implemented please reopen and set the target milestone to "next".
NetBeans.org Migration: changing resolution from LATER to WONTFIX