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.
E.g. Project Settings | Java Settings | Synchronization options canDestroy(). In fact "deleting" the node does nothing, but it should not even be enabled. To disable it, probably it will be necessary to turn off canDestroy() using a FilterNode in org.netbeans.core.ControlPanelNode. But it is strange that deleting it does nothing--since this is a BeanChildren perhaps there is also a bug in BeanChildren pertaining to destroying children (it ought to remove the child from the bean context).
Various other standard nodes were modifiable in undesirable ways as well. Fixed in trunk and release31. But BeanChildren not touched, probably this is still incorrect. Also org.netbeans.modules.url.BookmarksNode should have been updated correspondingly but was not.
Presumably still true in 3.1.
Target milestone -> 3.3
still true in [dev sep 17]
Filed some other bugs for related problems. Deletability of context sysop kids fixed: InstanceNode.java 1.14 System file system mount node should not be deletable: MountNode 1.8 Deleting a bean child (if permitted) should really remove it: BeanChildren 1.15 (with unit test added)
Resolved for 3.4.x or earlier, no new info since then -> verified
Resolved for 3.4.x or earlier, no new info since then -> closing.