Bug 488819 - Make o.e.handly dependency on o.e.core.resources optional
Summary: Make o.e.handly dependency on o.e.core.resources optional
Status: RESOLVED FIXED
Alias: None
Product: Handly
Classification: Technology
Component: Core (show other bugs)
Version: 0.5   Edit
Hardware: All All
: P3 enhancement
Target Milestone: 0.5   Edit
Assignee: Vladimir Piskarev CLA
QA Contact:
URL:
Whiteboard: breakingchange
Keywords: api
Depends on:
Blocks:
 
Reported: 2016-03-02 02:52 EST by Vladimir Piskarev CLA
Modified: 2016-03-02 03:18 EST (History)
0 users

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 Vladimir Piskarev CLA 2016-03-02 02:52:49 EST 
There appears to be some interest (see e.g. a comment to [1] by Tom Schindl) in being able to use Handly in Eclipse RCP applications where o.e.core.resources bundle might be unavailable.

Besides, reducing bundle dependencies is a good thing in general, although it often comes with a cost. I think it should be possible to make o.e.handly dependency on o.e.core.resources optional with minimal API and implementation changes based on the "outward impression" of late resolution of symbolic references a JVM must provide according to the JVMS.

For the record, o.e.emf.ecore, o.e.emf.common.ui, o.e.core.filebuffers (to name a few) also have an optional dependency on o.e.core.resources.

[1] https://pisv.wordpress.com/2015/01/19/on-m-theory-and-h-models-or-can-emf-fit-every-nail/
Comment 1 Vladimir Piskarev CLA 2016-03-02 03:18:54 EST 
Pushed to master:
http://git.eclipse.org/c/handly/org.eclipse.handly.git/commit/?id=03503f6d6bf388d077c12499fb421b98ee111ab0


Breaking change: IHandleDelta's getResourceDeltas() and getMarkerDeltas() may now return null.