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 44334 - IllegalStateException when changing bootclasspath of the project
Summary: IllegalStateException when changing bootclasspath of the project
Status: CLOSED FIXED
Alias: None
Product: editor
Classification: Unclassified
Component: Refactoring (show other bugs)
Version: 4.x
Hardware: PC Windows ME/2000
: P2 blocker (vote)
Assignee: issues@java
URL:
Keywords:
: 44832 (view as bug list)
Depends on:
Blocks: 42864
  Show dependency tree
 
Reported: 2004-06-04 10:17 UTC by Martin Ryzl
Modified: 2007-04-03 18:02 UTC (History)
0 users

See Also:
Issue Type: DEFECT
Exception Reporter:


Attachments
Exception (908 bytes, text/plain)
2004-06-04 10:17 UTC, Martin Ryzl
Details

Note You need to log in before you can comment on or make changes to this bug.
Description Martin Ryzl 2004-06-04 10:17:12 UTC
When using J2ME project with more than one
configuration after several configuration
switching it throws an exception.
Comment 1 Martin Ryzl 2004-06-04 10:17:50 UTC
Created attachment 15470 [details]
Exception
Comment 2 Martin Ryzl 2004-06-15 10:42:39 UTC
as I get the exception every time I use the IDE I'm increasing the
priority
Comment 3 Martin Matula 2004-06-21 12:55:28 UTC
Seems to be fixed - no longer occurs.
Comment 4 David Kaspar 2004-06-21 15:31:16 UTC
Sorry, but I can reproduce it in today build on WinXP machine.
Reopening.
Comment 5 Martin Matula 2004-06-21 23:10:06 UTC
I tried to reproduce it - installed several emulators (Nokia, WTK22,
21) but I couldn't. Anyway, I changed the code so that the IDE should
now be able to recover from the inconsistency that caused the
exception. Please verify.
Comment 6 Martin Matula 2004-07-19 00:04:48 UTC
*** Issue 44832 has been marked as a duplicate of this issue. ***
Comment 7 Jiri Prox 2005-07-19 10:00:39 UTC
Martine, can you, please, verify this issue? Thanks.
Comment 8 Martin Ryzl 2005-07-19 10:51:04 UTC
I can't remember seeing the problem since final release of 4.1.