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.
Throws an exception on startup that a node (Java Source) not under the root (Options) cannot be selected. Note this bug is intermittently reproducible - a second restart often succeeds, and a third fails again (some kind of race condition?). Attaching log file.
Created attachment 6980 [details] log file
It looks to me like problem with Option dialog. Feel free to reassign back if I am wrong.
Tim, you're running 3.4 beta3. Please try it with the 3.4 final. I remember a similar bug was fixed in the past, don't remember when though.
Unhappily this can appear in nb3.4 final. The problem is that Java Sources (or some others nodes) is removed from hierarchy between a node is obtained and a node is selected; a node is refreshed and has not any parent. Maybe, DataObject representing node is invalidated, but set valid on false is not called at all.
This bug strikes me as P1 or P2, not P3 - doing a perfectly normal thing leaves the IDE un-restartable or intermittently non-restartable. That's pretty serious. And do we know what other nodes may have this problem?
Seems to be triggered by the fix of issue #20699, though OptionsAction is still IMHO at fault for not checking what nodes it is setting the selection to before setting it. It would be interesting to know why this node is getting recreated - I have no idea - but in the meantime OptionsAction can avoid the actual error by checking all nodes in the node selection to confirm they are beneath the root node.
Something we would want to fix, I think. P2 does sound more appropriate. Workaround is presumably to delete $userdir/system/Windows/ or at least part of it.
commited a workaround in OptionsAction. The nodes are checked if are under root before are selected, if not that a warning is logged. (rev.1.42 /cvs/core/src/org/netbeans/core/actions/OptionsAction.java)
Jiri, you can remove the workaround.
The heart of problem (issue 27025) was fixed. I'm going to remove workaround from trunk. I close as works for me.
remove 3.4.1_candidate
the workaround was removed
*** Issue 27565 has been marked as a duplicate of this issue. ***
*** Issue 29302 has been marked as a duplicate of this issue. ***
verified - it works fine in [nb_dev](20030728)