Some Eclipse Foundation services are deprecated, or will be soon. Please ensure you've read this important communication.

Bug 252647

Summary: [plan] Flexible resources
Product: [Eclipse Project] e4 Reporter: DJ Houghton <dj.houghton>
Component: ResourcesAssignee: Project Inbox <e4.resources-inbox>
Status: RESOLVED FIXED QA Contact:
Severity: enhancement    
Priority: P4 CC: angvoz.dev, jamesblackburn+eclipse, jtk499, mantram, mlists, mober.at+eclipse, recoskie, yevshif
Version: 0.9Keywords: plan
Target Milestone: 0.9   
Hardware: All   
OS: All   
URL: http://wiki.eclipse.org/E4/Resources
Whiteboard:
Bug Depends on: 229633, 252996    
Bug Blocks:    

Description DJ Houghton CLA 2008-10-29 15:41:41 EDT
The Resource architecture that Eclipse uses has been criticized for being overly Java-centric and constraining for some use cases. We will generalize the Resource layer (and related areas, such as EFS) to better address these uses. [Workspace, Platform UI]
Comment 1 Martin Oberhuber CLA 2008-11-26 05:29:44 EST
Status on the work of the e4 resources working group can be found from the bugs that this one depends on, as well as the e4 Resources wiki here:

   http://wiki.eclipse.org/E4/Resources

Be sure to follow the meeting notes for latest information. The "Definition of Terms" is interesting for basic concepts, and the Plan, Goals and Work Items are interesting for additional ideas that have been discussed but not yet captured as tangible tasks in bugzilla.
Comment 2 John Arthorne CLA 2009-07-20 15:52:40 EDT
Work on this plan item is completed for the e4 0.9 release.
Comment 3 Chris Recoskie CLA 2009-07-21 09:35:48 EDT
Ok, I'm confused...

How is this fixed when it depends on 8 open bugs?
Comment 4 John Arthorne CLA 2009-07-21 11:23:25 EDT
I think the dependent bugs were intended to mark bugs that are potentially related to this plan item. In the end, we only did what people actually volunteered to implement, which was delivered for the 0.9 release: resource filter support, groups, drag and drop of links, project-specific path variables, and editing of existing linked resources. While there is an open ended set of things we could have done, I marked it fixed based on the significant amount of stuff that was done.