Bug 522710 - Create new plugin project does not add runtime and ui to dependencies
Summary: Create new plugin project does not add runtime and ui to dependencies
Status: RESOLVED WONTFIX
Alias: None
Product: PDE
Classification: Eclipse Project
Component: UI (show other bugs)
Version: 4.7   Edit
Hardware: PC Windows 10
: P3 enhancement (vote)
Target Milestone: 4.22   Edit
Assignee: PDE-UI-Inbox CLA
QA Contact:
URL:
Whiteboard:
Keywords: investigate
Depends on:
Blocks:
 
Reported: 2017-09-25 05:24 EDT by Wim Jongman CLA
Modified: 2021-09-07 06:56 EDT (History)
2 users (show)

See Also:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Wim Jongman CLA 2017-09-25 05:24:55 EDT
How to duplicate:

1. Create new plugin project
2. Uncheck activator generation
3. Check "this plugins makes contributions to the UI"
4. Uncheck api analysis
5. Rich client application NO

Press finish

Even though I have checked "this plugins makes contributions to the UI" the wizards fails to add

org.eclipse.core.runtime
org.eclipse.ui




-- Configuration Details --
Product: Eclipse 4.7.0.20170620-1800 (org.eclipse.epp.package.jee.product)Installed Features:
 org.eclipse.platform 4.7.0.v20170612-1255
Comment 1 Lars Vogel CLA 2021-09-06 10:32:50 EDT
The "UI" flag is only used for the template selection. 

It used to add org.eclipse.ui and runtime but that was wrong, as e4 plug-ins would not work with an eclipse.ui dependency.
Comment 2 Wim Jongman CLA 2021-09-07 06:50:44 EDT
(In reply to Lars Vogel from comment #1)
> The "UI" flag is only used for the template selection. 
> 
> It used to add org.eclipse.ui and runtime but that was wrong, as e4 plug-ins
> would not work with an eclipse.ui dependency.

I see. This behavior changed from the original implementation. It would be more clear if it forced you to go to the template selection when this flag is set. Just like the "rich client application" selection does.
Comment 3 Lars Vogel CLA 2021-09-07 06:56:45 EDT
Or we rename the label?