Some Eclipse Foundation services are deprecated, or will be soon. Please ensure you've read this important communication.
Bug 369237 - [Model] Are we using org.eclipse.e4.emf.xpath?
Summary: [Model] Are we using org.eclipse.e4.emf.xpath?
Status: RESOLVED FIXED
Alias: None
Product: Platform
Classification: Eclipse Project
Component: UI (show other bugs)
Version: 4.1   Edit
Hardware: PC Windows 7
: P3 normal (vote)
Target Milestone: ---   Edit
Assignee: Platform UI Triaged CLA
QA Contact: Paul Webster CLA
URL:
Whiteboard:
Keywords:
Depends on: 324954
Blocks:
  Show dependency tree
 
Reported: 2012-01-20 09:35 EST by John Arthorne CLA
Modified: 2014-07-03 14:57 EDT (History)
5 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 John Arthorne CLA 2012-01-20 09:35:48 EST 
Two bundles were inadvertently removed from org.eclipse.e4.rcp as part of some feature cleanup this week:

org.eclipse.e4.emf.xpath
org.apache.commons.jxpath

However there doesn't seem to be any effect of not having them there. According to Paul these are intended for supporting xpath expressions in declarative model contributions, but he didn't think we actually supported that syntax yet. From bug 324954 it looks like this work is incomplete, and there is even discussion about moving it to somewhere in EMF. I'd rather not include something in the Juno RCP feature if we are not using it, and it is not usable in its current state. Beyond Juno it will be very difficult to ever remove this. 

So, is there any value in leaving this in the RCP feature for Juno. We can always re-introduce it later when the work in bug 324954 is complete.
Comment 1 Thomas Schindl CLA 2012-01-20 09:40:26 EST 
No you can remove it for Juno
Comment 2 Lars Vogel CLA 2014-07-03 14:57:29 EDT 
(In reply to Thomas Schindl from comment #1)
> No you can remove it for Juno

Sounds like their is nothing left to do.