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 80632 - Exception when creating JUnit test during MDR scan
Summary: Exception when creating JUnit test during MDR scan
Status: CLOSED WONTFIX
Alias: None
Product: javame
Classification: Unclassified
Component: JUnit (show other bugs)
Version: 5.x
Hardware: All Windows XP
: P3 blocker (vote)
Assignee: Jiri Prazak
URL:
Keywords:
Depends on: 80712
Blocks:
  Show dependency tree
 
Reported: 2006-07-19 16:01 UTC by Fabiola Rios
Modified: 2009-01-15 13:31 UTC (History)
0 users

See Also:
Issue Type: DEFECT
Exception Reporter:

Attachments
exception (1.07 KB, application/octet-stream)
2006-07-19 16:03 UTC, Fabiola Rios 		Details
NPE stacktrace (3.92 KB, text/plain)
2006-08-29 15:03 UTC, Lukas Hasik 		Details
I have a some problem. I attached my log file. (68.13 KB, text/plain)
2006-09-14 03:39 UTC, dgofman 		Details
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 Fabiola Rios 2006-07-19 16:01:53 UTC 
java.lang.NullPointerException when create JUnit test for MIDPCanvas.
	

See attachments
Comment 1 Fabiola Rios 2006-07-19 16:03:18 UTC 
Created attachment 32007 [details]
exception
Comment 2 Jiri Prazak 2006-07-20 13:00:13 UTC 
I cannot reproduce this issue. Neither can Lukas. It could be caused by 80712.
Comment 3 Lukas Hasik 2006-08-08 09:13:35 UTC 
I was able to reproduce it.
It can be reproduce when the the MDR repository is rebuilding. I'm attaching
longer stacktrace. 

Is it possible to block the test generation for a while or is it really manged
by JUnit module?
Comment 4 Martin Ryzl 2006-08-08 09:48:57 UTC 
I believe it is possible to disable actions during classpath scanning. Reopening.
Comment 5 Jiri Prazak 2006-08-08 18:09:28 UTC 
I do not own the action so I cannot disable it, JUnit does.  They should check
if any scan processes are in progress and turn the action on/off accordingly.
Comment 6 Martin Ryzl 2006-08-08 18:13:18 UTC 
please verify if the problem happen when using JUnit and J2SE project.
Comment 7 Jiri Prazak 2006-08-08 18:13:44 UTC 
The action should be disabled because when user clicks it, he expects results. 
By waiting for the MDR the generation could be postponed for a very long time
(especially during startup cycles).  The user will still be able to do other
stuff in the IDE but then new tests will "magically" appear a minute later, not
the best approach.
Comment 8 Lukas Hasik 2006-08-29 15:03:43 UTC 
Created attachment 33364 [details]
NPE stacktrace
Comment 9 Lukas Hasik 2006-08-29 15:05:43 UTC 
build 0829
I got a little bit different stacktrace. It contains a javacore exception too.
Maybe it can help. There wasn't any mdr scan running
Comment 10 dgofman 2006-09-14 03:39:15 UTC 
Created attachment 33922 [details]
I have a some problem. I attached my log file.
Comment 11 Lukas Hasik 2007-01-17 13:35:05 UTC 
5.5 is out. 
It has no sense to have some issues planned to be fixed in finished release.
Therefore I'm setting the Target Milestone back to TBD for futher evaluation
Comment 12 Jiri Prazak 2007-03-26 16:47:05 UTC 
this problem should not occur with the new java source model infrastructure,
therefore i will close the issue. should it reappear in 6.0, we can open a new
issue.
Comment 13 Fabiola Rios 2007-04-27 09:40:34 UTC 
verified 20070426 
ok
Comment 14 Ivan Sidorkin 2009-01-15 13:31:33 UTC 
closing old issues