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.
Summary: | WARNING [org.openide.filesystems.Ordering]: Not all children in Menu/Edit/ marked with the position attribute: [Separator3.instance] | ||
---|---|---|---|
Product: | platform | Reporter: | kiyut <kiyut> |
Component: | -- Other -- | Assignee: | issues@platform <issues> |
Status: | RESOLVED FIXED | ||
Severity: | blocker | CC: | mslama |
Priority: | P4 | ||
Version: | 6.x | ||
Hardware: | PC | ||
OS: | All | ||
Issue Type: | DEFECT | Exception Reporter: |
Description
kiyut
2007-11-10 02:49:55 UTC
Reassigning to openide. kiyut, it seems to me that it is up to you to assign the position to menu items... Could you provide more details about the issue? 1, does the issue appear in NB IDE 6.0? 2, did you add a menu items to the Menu/Edit? 3, this is just warning thank you Could you provide more details about the issue? 1, does the issue appear in NB IDE 6.0? Yes, it is appear on Netbeans 6.0 2, did you add a menu items to the Menu/Edit? Yes, we are adding some menu items on Menu/Edit, however the warning is about Separator3.instance on Menu/Edit, we did not add Separator3.instance. So my guess is some module on platform cluster are not using the new position attribute for the menu item Separator3.instance.. Unfortunately, I didn't know which module in platform cluster is adding the Separator3.instance. Note: this warning also appear on our own module if we did not using new position attribute (if we are still using the old node eg: <attr name="menuItem1.shadow/menuItem2.shadow" boolvalue="true"/>), however, after converting all our added menu item entries into the new position attribute. It is no longer have warning, only Separator3.instance warning (we did not add the Separator3.instance) 3, this is just warning Yes it is only warning, not an error no more incomplete ... moving opened issues from TM <= 6.1 to TM=Dev Seems fixed in current dev build 090331. I do not see any similar warning now. |