Community
Participate
Working Groups
Developing with the RCP, I tried to use some of the Eclipse standard views. The console would give me the message "could not create view: org.eclipse.ui.views.ContentOutline", for example. I launch the app through Run - Debug and check "Choose plug-ins and fragments to launch from the list". I select my app and then click "Add Required Plug-ins", "Apply", "Debug". I finally figured out that I need to manually add the plug-in org.eclipse.ui.views. It would be nice if the console message were a bit more descriptive or the plug-in was added when clicking on "Add Required Plug-ins".
Your plug-in does not explicitly list org.eclipse.ui.views as a dependency and that is why the "Add Required Plug-ins" does not add it. So if you want views, you have to add it manually. The Platform/UI behavior is reasonable. It does not make a big production when a plugin is missing. The view will just say that there was an error creating the view. This error could be anything, and if you check the log you could see the reason why. Moving to Platform/UI to either continue the discussion or close.
This is admittedly confusing because the ids for views that previously existed in the workbench in 2.1 are defined as constants in IPageLayout, and are not deprecated. Should deprecate all the ids in IPageLayout and define them in constant pools in the appropriate plugins. Not for 3.0, unfortunately, because we are API frozen and are only fixing critical bugs at this point.
Should add an entry to the RCP FAQ for this.
As of now 'LATER' and 'REMIND' resolutions are no longer supported. Please reopen this bug if it is still valid for you.
