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.
Found same position 200 for both Loaders/text/x-java/Actions/java-project-separator-1.instance and Loaders/text/x-java/Actions/org-netbeans-modules-graphicclassview-actions-GraphicViewAction.shadow Found same position 300 for both Loaders/text/x-java/Actions/Separator1.instance and Loaders/text/x-java/Actions/org-netbeans-modules-graphicclassview-actions-separatorAfter.instance
Fixed - 7668f29f5cbe (The more I see side effects like this and the issues with not being able to reorder things from other modules in layers, the less I think numeric position attributes were a good idea)
How is this a side effect? You picked a position that clashed with those of existing common menu items.
I didn't pick it, the new Action wizard did. A dirty workaround would be for the new Action wizard and friends always to use odd numbers, since all of the default NB ones seem to use multiples of 100. The point is, having to fix such collisions is a really pointless use of anyone's time that simply does not occur with relative ordering attributes.
The Action wizard ought to be picking numbers between the endpoints you selected in the position combo. If this is not working for you, please file a bug with steps to reproduce. It's not a pointless use of time; it's telling NB where you want your menu item to appear. Rather straightforward. By contrast, people spent a lot of time messing with relative ordering attributes which would routinely get broken just because a module was uninstalled, etc., and in fact these were rather harder for the IDE's wizards to deal with than the numbers are.