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.
I have project root and some packages marked with the cross in red area, but when I invoked Task List, there are no errors written. I also went through all files but no error was found. And when I opened the Task List for the first time, an exception reading java.lang.IllegalArgumentException: URI has a fragment component at java.io.File.<init>(File.java:370) at org.netbeans.modules.masterfs.MasterURLMapper.getFileObjects(MasterURLMapper.java:51) at org.openide.filesystems.URLMapper.findFileObject(URLMapper.java:188) ... appeared. But I am unable to reproduce it now. ----- NetBeans IDE Dev (Build 070423) 1.6.0_01; Java HotSpot(TM) Client VM 1.6.0_01-b06 Windows Vista version 6.0 running on x86 en_GB (nb); Cp1252
Created attachment 41533 [details] Exception Stacktrace
Created attachment 41534 [details] Screenshot
I can reproduce this. --- NetBeans IDE Dev (Build 070425) 1.6.0_01; Java HotSpot(TM) Server VM 1.6.0_01-b04 Linux version 2.6.12-1.1390_FC4smp running on i386 en_US (nb); UTF-8
*** Issue 103396 has been marked as a duplicate of this issue. ***
*** Issue 105619 has been marked as a duplicate of this issue. ***
I have experienced this as well. I see it in other projects from the NB sources as well even when they build and compile without issue. If these are about warnings in the code then I don't think it should be red, but should be yellow or something if warnings are all there is. I also think this issue needs to be a P2 as this needs to be addressed before release. We will get a lot of users seeing this, and the traffic on nbusers and IZ (bugs filed) will be ridiculous.
I'm not sure if this related, but I see a red box with a white exclamation mark on some of my package folders and I have no idea what they're about. One of them is on an empty package (see attached image). If you put red icons in the project tree, it implies there's some sort of error. There should be some sort of tooltip on the icon that explains why it's there! And, if it's not really an error that is being pointed out, it shouldn't be red.
Created attachment 47376 [details] image showing the red exclamation mark on an empty package
I've just found one reproducible case: 1) Create new J2SE project 2) Create new package with new file 3) Move one file from one package to the other result: The package from which the file was moved is marked with the error badge. Of course it is empty now so it doesn't make any sense. It seems to me that after moving (refactoring) any of class to another package, the original package is marked. Increasing priority to P2 as it is highly annoying that IDE claims there's an error even though there is none. And this state remains even after restart of IDE. The only way to correct it I found is to move the class back or to create class with similar name. ----- Product Version: NetBeans IDE 6.0 Beta 1 (Build 200709060000) Java: 1.6.0_02; Java HotSpot(TM) Client VM 1.6.0_02-b05 System: Windows Vista version 6.0 running on x86; Cp1252; en_GB (nb)
The problem with the move refactoring has been fixed as issue #115412. It may be still broken in some other cases, so keeping open.
*** Issue 116176 has been marked as a duplicate of this issue. ***
Renaming of files containing error should work OK now: Checking in test/unit/src/org/netbeans/modules/java/source/usages/RepositoryUpdaterTest.java; /cvs/java/source/test/unit/src/org/netbeans/modules/java/source/usages/RepositoryUpdaterTest.java,v <-- RepositoryUpdaterTest.java new revision: 1.4; previous revision: 1.3 done Checking in src/org/netbeans/modules/java/source/usages/RepositoryUpdater.java; /cvs/java/source/src/org/netbeans/modules/java/source/usages/RepositoryUpdater.java,v <-- RepositoryUpdater.java new revision: 1.88; previous revision: 1.87 done
*** Issue 116345 has been marked as a duplicate of this issue. ***
*** Issue 117407 has been marked as a duplicate of this issue. ***
*** Issue 116785 has been marked as a duplicate of this issue. ***
*** Issue 117856 has been marked as a duplicate of this issue. ***
Is this still valid in RC1?
Yes, this is still the issue of error badges showing up on files that have no errors. I'm attaching a screenshot. In it you can see the white exclamation marks on red background as well as one of the files with the supposed errors. As you can see from the right-hand gutter, there are no errors - only a warning on line 86 about adding an override annotation. All of the badges I see are of this nature: they show next to files with warnings, but not errors. I see them for: - unused imports - not annotating an overriding method - using an instance variable to call a static method etc. I guess it's ok to flag these files - but a little yellow warning triange badge should be used instead of a bright red one with an exclamation mark. Very misleading.
Created attachment 53017 [details] tree with error badges even though there are only warnings in the files
One additional finding - maybe important: When I close the tab of a file that has the error badge, the error badge magically goes away - even though I haven't changed the file at all!
Yesterday I opened #128614. I might be a duplicate of this one. It's probably at least related.
*** Issue 128617 has been marked as a duplicate of this issue. ***
*** Issue 128631 has been marked as a duplicate of this issue. ***
I'm currently trying out some module development, so moving around sometimes classes and packages. After moving, package often isn't corrected or some other errors appear because of broken relationships. After correcting the file, the error bage doesn't disappear before saving. Don't know about the internals, but looks for me as I'm only editing a copy, while the syntax check is still applied to the original (probably last saved) document.
Obviously not addressed in 6.0, please reevaluate.
Hi! I have this issue in 6.1 and 6.5Beta too. See atached image. Roti
Created attachment 69927 [details] still buggy
Still in 6.5, reevaluate please!
This issue is still valid. It is complex issue which needs complex fix.
*** Issue 128614 has been marked as a duplicate of this issue. ***
Reassigning all moonko's java/source bugs to myself.
If I understand correctly the claims in this issue it should be fixed as of now. If not please reopen with the exact scenario where the error badges are there and shouldn't.