Bug 462856 - refactoring: decouple org.eclipse.graphiti.ui from IDE depencency
Summary: refactoring: decouple org.eclipse.graphiti.ui from IDE depencency
Status: ASSIGNED
Alias: None
Product: Graphiti
Classification: Modeling
Component: Core (show other bugs)
Version: 0.12.0   Edit
Hardware: All All
: P3 enhancement (vote)
Target Milestone: ---   Edit
Assignee: Project Inbox CLA
QA Contact:
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2015-03-23 11:15 EDT by Flavio Donze CLA
Modified: 2015-03-24 05:11 EDT (History)
1 user (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 Flavio Donze CLA 2015-03-23 11:15:03 EDT 
The bundle "org.eclipse.graphiti.ui" has the following dependencies:

org.eclipse.ui.ide;bundle-version="[3.10.0,4.0.0)";resolution:=optional,
org.eclipse.ui.navigator;bundle-version="[3.5.400,4.0.0)",
org.eclipse.ui.views.properties.tabbed;bundle-version="[3.6.0,4.0.0)"

For graphiti integration in IDE independent RCP or even RAP applications, it would be great if those dependencies were moved to a separated bundle (e.g. org.eclipse.graphiti.ide).
It shouldn't be too complicated, doing a short analyse, I found these three classes with dependencies:
org.eclipse.graphiti.ui.platform.GFPropertySection
org.eclipse.graphiti.ui.editor.DiagramBehavior
org.eclipse.graphiti.ui.editor.DiagramEditor

It might be necessary to split up DiagramEditor, e.g. DiagramEditor / IDEDiagramEditor or the otherway DefaultDiagramEditor / DiagramEditor (which would not break existing applications).

Related Forum Post:
https://www.eclipse.org/forums/index.php/m/1684651/
Comment 1 Michael Wenz CLA 2015-03-24 05:10:27 EDT 
Thanks for this proposal. We could start with this earliest in summer with the next development cycle. Currently we are delivering the M6 milestone for Mars which is the API freeze milestone.

As always, contributions are highly welcome... ;-)

Michael