Bug 104836 - [API] [cdt.managedbuild.core] Managed build core plugin should not depend on UI
Summary: [API] [cdt.managedbuild.core] Managed build core plugin should not depend on UI
Status: ASSIGNED
Alias: None
Product: CDT
Classification: Tools
Component: cdt-build-managed (show other bugs)
Version: 3.0   Edit
Hardware: PC Windows 2000
: P3 normal (vote)
Target Milestone: ---   Edit
Assignee: Project Inbox CLA
QA Contact: Jonah Graham CLA
URL:
Whiteboard:
Keywords:
Depends on: 208952
Blocks:
  Show dependency tree
 
Reported: 2005-07-22 13:03 EDT by Jeremiah Lott CLA
Modified: 2020-09-04 15:16 EDT (History)
2 users (show)

See Also:

Attachments
Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.
Description Jeremiah Lott CLA 2005-07-22 13:03:37 EDT 
Currently the managed build plugin has a direct dependency on org.eclipse.ui.  
Several aspects of the code itself also assume an SWT GUI will be available.  
This is both a theory issue, where core plugins should be cleanly separated 
from GUI code, and a practical one.  The code in core that directly uses the 
GUI will make it impossible to write "headless" applications that use the 
managed build system.
Comment 1 Keith W. Campbell CLA 2008-02-13 10:38:39 EST 
Headless operation is enabled by the patch attached to bug 208484,
but the explicit dependency on org.eclipse.ui is still inappropriate.
Comment 2 Chris Recoskie CLA 2009-05-11 14:38:48 EDT 
This is a bit sticky.  I see a few places where these dependencies are used:

1.  When MBS tries to modify a file that is in version control, it needs to do so in a way that the user will be prompted to check out the file.
2.  When a project is converted from an older version of CDT, the user must be prompted before the update happens.

I'm not sure of an easy way around either of those.
Comment 3 Andrew Gvozdev CLA 2010-01-28 11:31:06 EST 
(In reply to comment #2)
> 2.  When a project is converted from an older version of CDT, the user must be
> prompted before the update happens.
There is a bug 208952 filed against problem 2. Looks like it causes real problems.