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 40438 - Not compiled icon does not disapear after compilation
Summary: Not compiled icon does not disapear after compilation
Status: RESOLVED DUPLICATE of bug 40794
Alias: None
Product: java
Classification: Unclassified
Component: Unsupported (show other bugs)
Version: 3.x
Hardware: PC Windows XP
: P3 blocker (vote)
Assignee: issues@java
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2004-02-25 01:33 UTC by levmatta
Modified: 2007-09-26 09:14 UTC (History)
0 users

See Also:
Issue Type: DEFECT
Exception Reporter:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description levmatta 2004-02-25 01:33:47 UTC
Java Source file node not compiled icon does not 
go away after compilation. It is apearing 
correctly after source changing, but sometimes 
does not disapear.
I have tried avery thing from compiling single 
files with F9, to groups of files using the 
filesystems view. Build also leaves the icon in 
place.

Thanks.
Comment 1 Milan Kubec 2004-02-25 08:10:20 UTC
Please evaluate.
Comment 2 levmatta 2004-02-26 01:01:24 UTC
Are you talking with me? If yes, what do you whant?
Comment 3 Jan Pokorsky 2004-02-26 11:13:41 UTC
No it was for developers. Anyway could you be more specific?

Is it reprodusible with whatever file or you have some special use case?  
Is the file under some VCS filesystem?
Does it occur for newly created class or just after the ide startup?
Comment 4 levmatta 2004-02-29 21:14:09 UTC
Compiling local files. I have 4 mounted folders (tests, src, build, 
docs). You can see that I have separeted sources and class files.
Normaly the files are going only through comment changes (so they 
dont actually get new compilations).
I tried with new classes and it is the same thing.

It is really strange.
Comment 5 Jan Pokorsky 2004-03-11 17:31:18 UTC
That's it. Separate .java and .class file seem to induce the problem.

*** This issue has been marked as a duplicate of 40794 ***