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 174821 - [68cat] [scanning] Project close should not require full project rescanning
Summary: [68cat] [scanning] Project close should not require full project rescanning
Status: RESOLVED DUPLICATE of bug 165093
Alias: None
Product: ruby
Classification: Unclassified
Component: Code (show other bugs)
Version: 6.x
Hardware: PC Linux
: P3 blocker (vote)
Assignee: Erno Mononen
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2009-10-18 05:27 UTC by esmithbss
Modified: 2010-04-13 15:42 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 esmithbss 2009-10-18 05:27:30 UTC 
[ BUILD # : 200910161401 ]
[ JDK VERSION : 1.6.* ]

I had 4 separate projects open within 200910161401.  When I closed
one project, the IDE began a "Scannint Projects" cycle on the other 3
projects (none of which have any interproject dependencies).

Based on discussions with Erno, I believe the project info should be
partitioned to allow project info to be managed separately.  If this
is the case, then this would appear to be over-zealous use of a
trigger to rescan projects every time the project tree changes (this
action should just clear out project specific scan data).

If  on the other hand, the project info cannot be separated by
project when multiple unrelated projects are open, then (IMO) there
is room for performance improvement within the scan data indexing.
Comment 1 Erno Mononen 2009-10-19 19:37:03 UTC 
Thanks for the report, this definitely should not be happening. Seems like a bug in the indexing infrastructure, I will 
investigate more tomorrow and reassign this if needed.
Comment 2 Erno Mononen 2010-04-13 15:42:04 UTC 

*** This bug has been marked as a duplicate of bug 165093 ***