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 50928 - Null Pointer Exception in Refactor Wizard
Summary: Null Pointer Exception in Refactor Wizard
Status: RESOLVED FIXED
Alias: None
Product: editor
Classification: Unclassified
Component: Refactoring (show other bugs)
Version: 4.x
Hardware: PC Windows XP
: P3 blocker (vote)
Assignee: Jan Becicka
URL:
Keywords: RANDOM
Depends on:
Blocks:
 
Reported: 2004-10-27 21:46 UTC by krisr
Modified: 2007-04-03 18:02 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 krisr 2004-10-27 21:46:32 UTC 
Whle running thru the QuickStart Guide, was at 
the step in the Refactoring section when I had 
dragged the Main.java to the new package and a 
wizard had popped up. I clicked on the first 
Next Button and got the following exception in 
the refactoring wizard:

Annotation: Exception occurred in Request 
Processor
java.lang.NullPointerException
	at 
org.netbeans.modules.refactoring.api.MoveClassRef
actoring.getEmptyPackages
(MoveClassRefactoring.java:258)
Comment 1 Martin Matula 2004-10-28 09:12:43 UTC 
Could you please attach messages.log and tell us what build you were
using? TIA
Comment 2 Jan Becicka 2004-10-29 08:06:34 UTC 
I'm not able to reproduce it. Stack trace seems to be obsolete. Is it
beta2 build?
Comment 3 krisr 2004-11-03 01:27:09 UTC 
Yes I'm using 4.0 Beta 2. I keep having a problem that requires me 
to reinstall the application to fix, so I no longer have the log 
file. When I reinstall again, I'll try to reproduce and will attach 
the log files.
Comment 4 krisr 2004-11-03 02:02:05 UTC 
Don't see the error with a clean install. Next time netBeans 
requires a fresh install, would you like me to attempt again and 
attach a log if I see the problem?
Comment 5 Martin Matula 2004-11-03 08:54:52 UTC 
This is due to the inconsistency bugs we had in beta 2. Most likely it
was already fixed. You should probably get a newer build to get rid of
these exceptions. You can try either one of the recent dev builds or
the latest q-build.
Comment 6 Jan Becicka 2004-11-05 08:33:46 UTC 
OK, closing as fixed. It was probably caused by inconsistency bugs.
Krisr, if this bug happens again, please reopen this issue and attach
your $USER_DIR$/var/log/messages.log file. Thanks.