Community
Participate
Working Groups
Build Identifier: I20100429-1549 It seems that there's a category reference coming from the cocoa fragment for org.eclipse.ui which pointing to a category defined in org.eclipse.ui.cheatsheets: http://dev.eclipse.org/viewsvn/index.cgi/org.eclipse.ui.cocoa/fragment.xml?view=markup As a result, simply creating a new RCP application by means of e.g. the "Hello RCP" template and then hitting start without further ado results in a unnecessary warning message being dumped to the user's console: !ENTRY org.eclipse.ui 2 0 2010-05-06 21:23:30.561 !MESSAGE Warnings while parsing the commands from the 'org.eclipse.ui.commands' and 'org.eclipse.ui.actionDefinitions' extension points. !SUBENTRY 1 org.eclipse.ui 2 0 2010-05-06 21:23:30.562 !MESSAGE Commands should really have a category: plug-in='org.eclipse.ui', id='org.eclipse.ui.cocoa.closeDialog', categoryId='org.eclipse.ui.category.dialogs' One would think that the org.eclipse.ui.category.dialogs category should either belong to org.eclipse.ui instead of org.eclipse.ui.cheatsheets or the cocoa shouldn't reference this category after all. Reproducible: Always Steps to Reproduce: 1. Create an empty RCP application on MacOSX Cocoa 2. Start with minimal plug-ins (that is, no org.eclipse.ui.cheatsheets)
Created attachment 167660 [details] Patch v01
Can this fix be considered for 3.6 or 3.6.1?
(In reply to comment #2) > Can this fix be considered for 3.6 or 3.6.1? Yes, when we fix it for 3.7, we will backport to 3.6.1
The org.eclipse.ui.carbon fragment looks identical, so it is also affected.
(In reply to comment #4) > The org.eclipse.ui.carbon fragment looks identical, so it is also affected. Right the patch in comment #1 addresses carbon as well
Patch v01 released to HEAD
(In reply to comment #3) > (In reply to comment #2) > > Can this fix be considered for 3.6 or 3.6.1? > > Yes, when we fix it for 3.7, we will backport to 3.6.1 Prakash, are you still considering this bug for the 3.6.x maintenance stream or will you not be backporting the fix?
I can confirm it is fixed in 3.6.1.
(In reply to comment #8) > I can confirm it is fixed in 3.6.1. Thanks Adriaan. 3.6 maintenance stream is tracked in Bug# 322887