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.
Summary: | Race condition in Fix Imports | ||
---|---|---|---|
Product: | java | Reporter: | _ gtzabari <gtzabari> |
Component: | Editor | Assignee: | Jan Lahoda <jlahoda> |
Status: | RESOLVED WONTFIX | ||
Severity: | blocker | CC: | msauer |
Priority: | P4 | Keywords: | RANDOM |
Version: | 6.x | ||
Hardware: | All | ||
OS: | All | ||
Issue Type: | DEFECT | Exception Reporter: |
Description
_ gtzabari
2009-01-09 23:19:30 UTC
Reassigning to editor. Thanks for the report. I tried to reproduce it in a dev build, but without success. Product Version: NetBeans IDE Dev (Build 090115) Java: 1.5.0_14; Java HotSpot(TM) Client VM 1.5.0_14-b03 System: Linux version 2.6.22-16-generic running on i386; UTF-8; en_US (nb) Userdir: /home/vita/devel/netbeans/main/nbbuild/testuserdir I'm curious, did you inspect the code for any sort of synchronization between: 1) Exporting new imports when the Fix Imports dialog is closed, and 2) Scanning existing imports before the Fix Imports dialog comes up Random issues will definitely be hard to reproduce but if the code has no synchronization to begin with then we can fix the problem without fully reproducing it. I think this can happen. OTOH, the solution is simple: do not invoke the Fix All Imports action twice so quickly (I do not see the usecase for this anyway). So, fixing this does not seem like a big priority to me - there seem to be more urgent problems to fix. However, feel free to provide a patch. Users need to invoke Fix Imports multiple times quickly because sometimes the first invocation does not resolve all the missing imports. For example, if you have an anonymous class then the first invocation of Fix Imports will resolve classes outside the class, the second invocation will resolve inside the class. At least, that's been my experience. NetBeans.org Migration: changing resolution from LATER to WONTFIX |