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 13133 - Explorer filesystem does not refresh correctly
Summary: Explorer filesystem does not refresh correctly
Status: CLOSED DUPLICATE of bug 11183
Alias: None
Product: java
Classification: Unclassified
Component: Unsupported (show other bugs)
Version: 3.x
Hardware: PC Windows ME/2000
: P3 blocker (vote)
Assignee: issues@projects
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2001-06-23 00:34 UTC by emmanuel
Modified: 2007-09-26 09:14 UTC (History)
0 users

See Also:
Issue Type: DEFECT
Exception Reporter:

Attachments
Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.
Description emmanuel 2001-06-23 00:34:56 UTC 
NB Build 200106220100.

Usually with CVS refreshing/refreshing recursively, the .java file badge (I 
think its called a badge) indicates whether or not it is in line with 
the .class file.

Well some do and some don't.

Could this be corrected please.

Kind regards
Emmanuel
Comment 1 emmanuel 2001-06-23 00:59:42 UTC 
It seems that only once the .java file that show their status incorrectly are 
opened in the Source Editor are they 'refreshed' and then their 'status' shows 
correctly.

BTW this is already the case in build 200106200100.

Kind regards
Emmanuel
Comment 2 emmanuel 2001-06-23 01:18:47 UTC 
Please note, I use target directory when compiling.
Comment 3 Jan Chalupa 2001-06-25 13:51:26 UTC 
Re-assigning to java.

Is this really a P1? Is the user's productivity seriously affected or can her 
data get lost? I'd say P3.
Comment 4 Jan Becicka 2001-06-25 14:05:05 UTC 
This problem is not pertinent to CVS nor projects, I think. The same behavior 
was observed on local filesystem.


*** This issue has been marked as a duplicate of 11183 ***
Comment 5 emmanuel 2001-06-25 14:16:57 UTC 
Hello Jan,

Nothing was lost, however, the misinformation creates the impression that 
Explorer details are unreliable, especially in the light of a previously 
reported issue #12914.

I propose either P1 or P2.

Kind regards
Emmanuel
Comment 6 Jan Becicka 2001-06-25 14:51:31 UTC 
P1 and P2 are priorities, that we use for data loss, deadlocks or issues, which 
are blocking work in IDE. Wrong badge gives wrong information, but this 
information is not necessary for development. I agree with Jan Chalupa, that P3 
is appropriate priority.
Comment 7 emmanuel 2001-06-25 14:59:19 UTC 
Point taken, thank you.
Comment 8 Quality Engineering 2003-07-01 13:11:06 UTC 
Resolved for 3.3.x or earlier, no new info since then -> closing.
Comment 9 Quality Engineering 2003-07-01 13:20:52 UTC 
Resolved for 3.4.x or earlier, no new info since then -> closing.