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 47577 - [40cat] Problem when switching from WTK to Siemens toolkit
Summary: [40cat] Problem when switching from WTK to Siemens toolkit
Status: CLOSED WORKSFORME
Alias: None
Product: javame
Classification: Unclassified
Component: -- Other -- (show other bugs)
Version: 4.x
Hardware: PC Windows XP
: P3 blocker (vote)
Assignee: Adam Sotona
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2004-08-20 17:11 UTC by malakim
Modified: 2006-10-23 16:41 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 malakim 2004-08-20 17:11:27 UTC 
[ BUILD # : 200408191352 ]
[ JDK VERSION : J2SE 1.5.0 ]

After installing the Siemens mobility toolkit 2.00.3b as the target platform for my project, the IDE keeps displaying the "Scanning project classpath" dialog. The only way to escape is to kill the IDE using Task Manager.

After a restart of the IDE, it's possible to switch between WTK 2.2 and Siemens toolkits without further problems. This seems only to happen when the first emulator is added, as adding the Sony Ericsson toolkit didn't produce this error, and removing and adding of emulators doesn't produce an error.
Comment 1 Adam Sotona 2004-08-23 09:49:25 UTC 
Could you please attach a thread dump when this happens, I am not able
to reproduce the problem.
Please start NetBeans using nb.exe -userdir <some_nonexisting_dir> to
simulate the first start, try to reproduce the problem, and press
CTRL+Break in terminal window to get actual thread dump when it hangs up.
This will help us a lot to resolve the problem.
Comment 2 malakim 2004-08-24 16:21:38 UTC 
Hmm... I can't seem to reproduce it either. I'll try removing all
NetBeans stuff and do a fresh install, to see if that makes the
problem reappear.
Comment 3 malakim 2004-08-24 17:20:12 UTC 
I tired making a clean install, and I still can't reproduce the
problem. Probably it was just some temporary problem, as no one else
has noticed it (at least not that I am aware of).
Comment 4 Lukas Hasik 2004-09-10 12:59:55 UTC 
Malakim, I'm closing this issue as worksforme.
Feel free to reopen when it reappears or you'll have a stacktrace. 
Thanks for report.
Comment 5 Lukas Hasik 2005-04-22 10:42:21 UTC 
closing