Community
Participate
Working Groups
When a nested wizard category is created, wizards must specify the full category path to be placed in that category. We should allow the simple category ID to be used, since the category nesting has already been specified. For more details, see 1GFXW2V: ITPUI:ALL - Nested Categories in New Wizard does not work propely NOTES:
PRODUCT VERSION: 0.9
This is confusing for wizard authors and should be fixed. Should wait until new project natures story is done though.
Defer until next release
Reopen for investigation
Not for 3.0
Reopening now that 3.0 has shipped
*** Bug 23902 has been marked as a duplicate of this bug. ***
Eric mentioned we should be sure that implementing this feature preserves the customization behaviour that's currently provided by the CPD. Fixing this should mean that the PDE id pointer thingy will work properly for child categories, will need to confirm and verify this though.
If we allow the child category to be specified instead of the full path along with adding back the identifier attribute that was reverted by bug 255949, all current adopters that uses child categories will get the warning. If they alter the code to use the new way, their plug-in will no longer be backwards-compatible since pre-3.5 code cannot process the path recursively and will dump it in the 'Other' category. Paul, is this a problem? Or would this be similar to saying "well, you can use this deprecated API or you can use this new @since 3.5 API"?
(In reply to comment #9) > If we allow the child category to be specified instead of the full path along > with adding back the identifier attribute that was reverted by bug 255949, all > current adopters that uses child categories will get the warning. That should be bug 225949.
Prakash is now responsible for watching bugs in the [Wizards] component area.
This bug hasn't had any activity in quite some time. Maybe the problem got resolved, was a duplicate of something else, or became less pressing for some reason - or maybe it's still relevant but just hasn't been looked at yet. If you have further information on the current state of the bug, please add it. The information can be, for example, that the problem still occurs, that you still want the feature, that more information is needed, or that the bug is (for whatever reason) no longer relevant.
