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.
Hi, When I move a custom component's class to another package, the new location is not propagated to the MVD file, so after reloading of the file, the class can't be found and references to it are deleted. Another (already reported) issue, is that the generated code of MobPack uses FQN which prevents the class from being moved in the MVD's corresponding .JAVA file. Iwan
J2ME modules must implement their refactoring plugin.
This is not supported in current version of VMD. The palette is static right now. When an user is adding a component/Java_class into the palette, its abstraction is registered only. This abstraction does not synchronize with the original class and stays in the palette unchanged even when a class file is deleted. Lowering priority to P3 and changing to an ENHANCEMENT.
moving to mobility component
This issue requires "Live Palette" feature which is planned as optional for NetBeans 6.0. Lowering the issue to P3 enhancement. Setting Target Milestone to "Dev".
Designer 1 has been removed. Therefore reassigning to Designer 2 module. Probably this issue will be resolved in the future.
Required "Live Palette" feature has be removed from 6.0 plan. Very likely it will not be implemented in NB 6.0.