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 55806 - [41cat] Compile package keeps icons uncompiled
Summary: [41cat] Compile package keeps icons uncompiled
Status: RESOLVED DUPLICATE of bug 54856
Alias: None
Product: java
Classification: Unclassified
Component: Unsupported (show other bugs)
Version: 4.x
Hardware: Other Linux
: P3 blocker (vote)
Assignee: Tomas Zezula
URL:
Keywords: REGRESSION
Depends on:
Blocks:
 
Reported: 2005-03-02 22:52 UTC by johnzoet
Modified: 2007-09-26 09:14 UTC (History)
1 user (show)

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 johnzoet 2005-03-02 22:52:10 UTC 
[ JDK VERSION : 1.5.0_01 ]

When I compile a package the icons stay in 
uncompiled mode. 
When I compile each source file individually 
they uncompiled icon goes away.
Comment 1 Petr Nejedly 2005-03-03 10:01:00 UTC 
Java node probably doesn't fire icon change.
Maybe it doesn't get an event from underlaying layer (SFBQ)

Anyway, it seems to be fixed already (as of 3/3/2005).
Passing to java for evaluation, feel free to close as a duplicate of
exising issue
Comment 2 Jan Becicka 2005-03-04 07:57:51 UTC 
Probably bug in FileBuiltQuery.
It is reproducible. BTW see issue 54856.
Comment 3 Tomas Zezula 2005-03-04 08:34:16 UTC 

*** This issue has been marked as a duplicate of 54856 ***
Comment 4 Milan Kubec 2005-03-05 15:55:38 UTC 
It seems to be reproducible for me on build dev-200503031900. I'm not
sure that it's really duplicate of #54856, behavior is a bit
different. Please evaluate again.
Comment 5 Tomas Zezula 2005-03-07 09:57:46 UTC 
In my opinion it is a duplicate, btw. it did not work for Honza even
in build you have verified it.
Comment 6 Milan Kubec 2005-03-07 10:39:58 UTC 
I've verified the fix of #54856 in dev-200502231900 and Honza
reproduced this issue on 2005-03-03 so it might be easily another bug.
Or if you are confident that it's duplicate, OK, but then reopen the
issue it is duplicated to. You shouldn'd duplicate curently
reproducible bug to issue that is already marked as fixed and verified.
Comment 7 Milan Kubec 2005-03-07 10:45:59 UTC 
Maybe really duplicate, I'm reopening #54856.

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