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.

Bug 46891 - Badging of java nodes for compiled state is unreliable
Summary: Badging of java nodes for compiled state is unreliable
Status: CLOSED FIXED
Alias: None
Product: java
Classification: Unclassified
Component: Unsupported (show other bugs)
Version: 4.x
Hardware: PC Windows ME/2000
: P3 blocker (vote)
Assignee: Jan Becicka
URL:
Keywords: RANDOM
Depends on:
Blocks:
 
Reported: 2004-08-04 13:16 UTC by Antonin Nebuzelsky
Modified: 2007-09-26 09:14 UTC (History)
0 users

See Also:
Issue Type: DEFECT
Exception Reporter:


Attachments
Screenshot 1 (66.20 KB, image/png)
2004-08-04 13:19 UTC, Antonin Nebuzelsky
Details
Screenshot 2 (102.19 KB, image/png)
2004-08-04 13:19 UTC, Antonin Nebuzelsky
Details
Log demonstrating problem; note also that icons for some files are apparently updated several times for no real reason (10.12 KB, text/plain)
2004-08-05 23:04 UTC, Jesse Glick
Details

Note You need to log in before you can comment on or make changes to this bug.
Description Antonin Nebuzelsky 2004-08-04 13:16:41 UTC
When you start the IDE with a package expanded in
the explorer and a file from the package open in
the editor the badges marking java files as
uncompiled are missing, only the opened file has
the badge.

This is not 100% reproducible but happens almost
always.

See two screenshots with the state after start
without any files open and the state after start
with a file open...
Comment 1 Antonin Nebuzelsky 2004-08-04 13:19:14 UTC
Created attachment 16640 [details]
Screenshot 1
Comment 2 Antonin Nebuzelsky 2004-08-04 13:19:39 UTC
Created attachment 16641 [details]
Screenshot 2
Comment 3 Jan Becicka 2004-08-04 13:29:59 UTC
Build system issue. Tomas, please take a look at it. Thanks.
Comment 4 Jan Becicka 2004-08-04 13:57:44 UTC
Duplicate of issue 45694?
Comment 5 Tomas Zezula 2004-08-04 14:26:08 UTC
Reassigning to Jesse, it seems as a problem of
FileBuildQueryImplementation.
Comment 6 Jesse Glick 2004-08-04 18:44:09 UTC
I will see if I can reproduce it.
Comment 7 Jesse Glick 2004-08-05 23:03:12 UTC
Yes, I can reproduce it, in a dev build, JDK 1.4.2, w/ one unbuilt
j2seproject open with classes (all expanded in Projects tab):

testanttaskwiz.Fo2
testanttaskwiz.Foo1
testanttaskwiz.Hey1
testanttaskwiz.Hey2
testanttaskwiz.Main
testanttaskwiz.NoWay
testanttaskwiz.yoyo.Yeahway

I have Main and Hey2 open in the editor, with Hey2 selected. When I
restart the IDE, all classes except Main have the compile badge
displayed. If I switch to Main, it gets a badge suddenly. This is
quite repeatable, i.e. not a timing issue.

Tracked it down as far as JavaNode.resolveIcons, which sometimes gets
null from JMManager and then quietly returns without going on to call
resolveCompileBadge. See example log w/ debug messages.
Comment 8 Jesse Glick 2004-08-05 23:04:26 UTC
Created attachment 16666 [details]
Log demonstrating problem; note also that icons for some files are apparently updated several times for no real reason
Comment 9 Jan Becicka 2004-08-06 10:22:27 UTC
Compile badges are now reslved regrdless of JMManager.getResource()

Checking in JavaNode.java;
/cvs/java/src/org/netbeans/modules/java/JavaNode.java,v  <-- 
JavaNode.java
new revision: 1.111; previous revision: 1.110
done
Comment 10 Antonin Nebuzelsky 2004-08-06 14:19:16 UTC
Seems to be fixed. I did not encounter it anymore.