Some Eclipse Foundation services are deprecated, or will be soon. Please ensure you've read this important communication.
Bug 348818 - Empty Design menu
Summary: Empty Design menu
Status: RESOLVED WORKSFORME
Alias: None
Product: Platform
Classification: Eclipse Project
Component: UI (show other bugs)
Version: 4.1   Edit
Hardware: PC Mac OS X - Carbon (unsup.)
: P3 normal (vote)
Target Milestone: ---   Edit
Assignee: Platform-UI-Inbox CLA
QA Contact:
URL:
Whiteboard:
Keywords:
Depends on:
Blocks: 334303
  Show dependency tree
 
Reported: 2011-06-08 17:54 EDT by Bryan Hunt CLA
Modified: 2012-01-11 14:33 EST (History)
2 users (show)

See Also:


Attachments
menubar screenshot (27.36 KB, image/jpeg)
2011-06-08 17:55 EDT, Bryan Hunt CLA
no flags Details

Note You need to log in before you can comment on or make changes to this bug.
Description Bryan Hunt CLA 2011-06-08 17:54:30 EDT
I downloaded 4.1RC3 installed some features from Indigo p2 repo, and now I have
an empty Design menu in the menubar.  The features I installed are:

DataTools
EMF SDK
JavaScript Development Tools
M2E
Marketplace Client
Mylyn
Web Page Editor
Comment 1 Bryan Hunt CLA 2011-06-08 17:55:00 EDT
Created attachment 197655 [details]
menubar screenshot
Comment 2 Bryan Hunt CLA 2011-06-08 17:57:04 EDT
I just discovered that if I switch from the Package Explorer view to another view and back again, the empty Design menu goes away.
Comment 3 Dean Roberts CLA 2011-07-14 15:40:31 EDT
As a data point, I just tried this on Windows 7 using 4.1 I20110705-1340.  Installed the same bundles listed in the defect (except I wasn't sure which of the many Mylan bundles, I "randomly" picked Mylan Context Connetor: Eclipse IDE.

I do not see an Design menu item.

Also I noticed the screen shot had 2 source and 2 refactor menus too.  I'm guessing this is not normal.
Comment 4 Paul Webster CLA 2011-07-14 15:56:45 EDT
This might be fixed as part of Bug 348817 which was done right at the end of R4.1

PW
Comment 5 Remy Suen CLA 2012-01-11 14:33:15 EST
Should no longer be an issue on the recent builds of 4.2.

Please let us know if you're still seeing this problem, Bryan.