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 165090 - bugzilla new-subcomponent cache/refresh issue
Summary: bugzilla new-subcomponent cache/refresh issue
Status: RESOLVED INVALID
Alias: None
Product: connecteddeveloper
Classification: Unclassified
Component: Bugzilla (show other bugs)
Version: 6.x
Hardware: All All
: P4 blocker (vote)
Assignee: Tomas Stupka
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2009-05-13 16:39 UTC by mikee11
Modified: 2009-07-27 09:20 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 mikee11 2009-05-13 16:39:02 UTC 
the subcomponent inside a bugzilla "product" are only updated after netbeans if restarted. (not when a new ticket is
opened, or an existing ticket is refreshed).

To replicate:
 -- open NB, and try to create a new issue against an bugzilla instance.
 -- as a bugzilla administrator go directly to the bugzilla GUI, and create a new "subcomponent" to that "project".
 -- that option/subcomponent doesn't appear in NetBeans's "view" until netbeans is restarted.
Comment 1 Tomas Stupka 2009-05-13 18:11:59 UTC 
what build do you use? there was recently added a "Reload Attributes" button in the issue mask.
Comment 2 mikee11 2009-05-13 18:32:53 UTC 
Product Version: NetBeans IDE 6.7 Beta (Build 200904242137)
Java: 1.6.0_02; Java HotSpot(TM) Client VM 1.6.0_02-b06

Should I go to the nightlies and validate?
(the same issue with my current build happens when a new PROJECT is added. You don't see it until NB is restarted)

thanks -- MikeE
Comment 3 Tomas Stupka 2009-05-13 18:45:24 UTC 
> Should I go to the nightlies and validate?
you could give it a try:)

the change was pushed yesterday it's still not in the latest build, so maybe tomorrow...
Comment 4 mikee11 2009-05-13 18:47:47 UTC 
Excellent, would that cover both the NEW-component AND NEW-product caching issue?
Comment 5 Tomas Stupka 2009-05-13 19:03:36 UTC 
> Excellent, would that cover both the NEW-component AND NEW-product caching issue?
yes