Community
Participate
Working Groups
Build ID: 3.7m4 Up until Eclipse 3.7m3, I used a category.xml file where the category "name" aka "id" looked like this: <feature url="features/org.eclipse.rse.useractions_1.1.300.qualifier.jar" id="org.eclipse.rse.useractions" version="1.1.300.qualifier"> <category name="TM and RSE Main Features"/> </feature> <feature url="features/org.eclipse.rse.scp_0.1.0.qualifier.jar" id="org.eclipse.rse.scp" version="0.1.0.qualifier"> <category name="TM and RSE Optional Add-Ons"/> </feature> This worked fine both with the category.xml editor in the UI, and with the CategoryPublisher commandline app. Turned out that since Eclipse 3.7m4, this format is not recognized any more. The CategoryPublisher commandline app terminates with a failure message claiming it cannot read the category.xml "update site file". The category.xml editor remains completely empty when dbl clicking the old file. I had to re-create my file from scratch using the UI editor, coming up with this syntax that works: <feature url="features/org.eclipse.rse.useractions_1.1.300.qualifier.jar" id="org.eclipse.rse.useractions" version="1.1.300.qualifier"> <category name="tm_33_main"/> </feature> <feature url="features/org.eclipse.rse.examples_3.1.200.qualifier.jar" id="org.eclipse.rse.examples" version="3.1.200.qualifier"> <category name="tm_33_optional"/> </feature> I think that addressing this issue might be important, since I seem to remember that in the past there was some confusion about what the "name" of a category was versus the "label". I think that with old update manager, maybe the "name" turned up in the UI instead of the label, and that's why my old build had those funny names with the special chars.
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. -- The automated Eclipse Genie.
