Some Eclipse Foundation services are deprecated, or will be soon. Please ensure you've read this important communication.
Bug 368187 - Services pre-API cleanup
Summary: Services pre-API cleanup
Status: RESOLVED FIXED
Alias: None
Product: Platform
Classification: Eclipse Project
Component: UI (show other bugs)
Version: 4.2   Edit
Hardware: PC Windows 7
: P3 normal (vote)
Target Milestone: ---   Edit
Assignee: Platform UI Triaged CLA
QA Contact: Oleg Besedin CLA
URL:
Whiteboard: candidate43
Keywords:
Depends on: 403190
Blocks:
  Show dependency tree
 
Reported: 2012-01-09 13:29 EST by Oleg Besedin CLA
Modified: 2014-07-03 14:55 EDT (History)
4 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 Oleg Besedin CLA 2012-01-09 13:29:49 EST 
We need to decide what services we'll provide as APIs in 4.2.

The services we have have were seeded from 3.x and grown "organically" as we needed them. The result from API perspective is a mixed bag. Some services have gotten to be rather complex which impacts both development and runtime performance.

I'll use this bug as a "container" for the related changes. Things that immediately come to mind:
- what's the E4 headless app? Does it include the model?
- location for the common application code (currently in the org.eclipse.e4.ui.workbench.swt)
- we should simplify services. If we have about 600 tests for the EPartService, what does that say?
- mixed inter-dependencies. As as example, part service needs IPresentationEngine and calls it directly. 
- for to-be-API things we need to go over Javadocs - they are mostly not there
Comment 1 Oleg Besedin CLA 2012-01-09 13:47:57 EST 
Initial change - mostly updating tests to use common setup technique:

http://git.eclipse.org/c/platform/eclipse.platform.ui.git/commit/?id=a9ca9a2c35f6e030d6afca2a0e458789a66b59b9
Comment 2 Eric Moffatt CLA 2012-02-08 16:05:34 EST 
This work has been deferred to post-4.2. I'll set the milestone to M7 but this is simply because there is no 4.3 bucket yet...
Comment 3 Lars Vogel CLA 2014-07-03 14:55:54 EDT 
(In reply to Oleg Besedin from comment #0)
> We need to decide what services we'll provide as APIs in 4.2.

4.2 is done