Build: NetBeans IDE 6.5 Beta (Build 200808111757)
VM: Java HotSpot(TM) Client VM, 1.6.0-b105, Java(TM) SE Runtime Environment, 1.6.0-b105
OS: Windows XP, 5.1, x86
rgarske: Just starting up Netbeans IDE 6.5 Beta for the first time,
importing Settings from Netbeans IDE 6.1
By the way, the IDE shows lots of errors for projects that are perfectly OK in
GUEST: Editing java files. Netbeans reports errors in files (although there aren't any mistakes/compile errors). Project has custom ant script. Netbeans 6.5 Beta
GUEST: I was closing an unedited file in the editor pane.
I have been having a lot of problems with the UI showing compile errors when there are none. One way to get rid of the compile errors in the UI is to open the file and close it again (which is what I was doing when this error occured), but this doesn't always rectify the issue. Oftentimes I have to delete the netbeans chache to force a "UI recompile" to get the errors to go away. This is probably my biggest issue with the IDE (this was also present in 6.1).
Created attachment 73273 [details]
Is the issue reproducible on your sources?
Created attachment 123881 [details]
Created attachment 140723 [details]
this occures, when I type:
System.out.println(1 + ":\t" + ArrayList);
I reproduced this bug on a new java project.
In a method, add a line such as this one (followed or not by a code block):
if (MyClass != null)
MyClass being an *existing* class name.
114 reports => P2
Created attachment 146601 [details]
hg pull in console
Created attachment 146602 [details]
build in console
Created attachment 147022 [details]
I'm working on a Maven Java project.
In the pom.xml file I would like to comment a dependency to see how this library affects the project.
In the pom.xml I select the dependency code with the mouse:
and press <SHIFT>+<ALT>+C . The dependency in the pom.xml file is commented. When I press <CTRL>+S to save the modified pom.xml this exception is thrown
(In reply to Saucistophe from comment #5)
> In a method, add a line such as this one (followed or not by a code block):
> if (MyClass != null)
> MyClass being an *existing* class name.
> Crashes everytime.
Reproduced in dev version.
Created attachment 148399 [details]
Reproduced on dev build, running on JDK 7. Place the file into a project, make any text change and then save; the error will be produced during reindexing the changed file.
If I saw correctly in the debugger, the enter/attribute phase of the parser did *not* report any error diagnostic for the NewClass (regular compilation produces an error message that a variable was not found). Subsequently the code generator attempted to clone ClassSymbol which is undefined.
Fixed in jet-main. Thanks for the reproducible test case.
Integrated into 'main-silver', will be available in build *201408010001* on http://bits.netbeans.org/dev/nightly/ (upload may still be in progress)
User: Dusan Balek <email@example.com>
Log: Issues #152386 and #237828 fixed.