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

Bug 80396

Summary:	[plan item] Mapping logical views to physical files on disk
Product:	[Eclipse Project] Platform	Reporter:	Jim des Rivieres <jeem>
Component:	Resources	Assignee:	Platform-Resources-Inbox <platform-resources-inbox>
Status:	RESOLVED FIXED	QA Contact:
Severity:	enhancement
Priority:	P4	CC:	give.a.damus, gunnar, Michael.Valenta, nikolaymetchev, pahack, some_guy_coding, thomasf, vramaswa
Version:	3.0	Keywords:	plan
Target Milestone:	3.1
Hardware:	All
OS:	All
Whiteboard:
Bug Depends on:
Bug Blocks:	37723

Description Jim des Rivieres

2004-12-07 13:02:31 EST

In some cases, multiple distinct objects happen to be stored in a single file, 
like an archive. Conversely, in other cases, something that is logically a 
single object is stored across multiple files. This discrepancy between 
logical and physical creates problems for common operations such as searching, 
comparing, and versioning, which need to work in the physical realm. Eclipse 
should support some way of mapping between a logical view and the physical 
organization of files on disk. [Platform Core, Platform UI, Team]

Comment 1 Jim des Rivieres

2004-12-07 13:11:06 EST

Note: This plan item covers a subset of plan item bug 37723.

Comment 2 John Arthorne

2005-04-29 16:31:13 EDT

Work on this plan item is completed for 3.1. A follow-on item may be added to
the 3.2 plan for future work in this area.

Comment 3 Michael Valenta

2005-05-03 14:31:01 EDT

We have decided to remove the new Eclipse 3.1 API for mapping of logical 
models to resources.  While we think this API is a strong step in the right 
direction, there has not been sufficient testing and validation to give us 
confidence that the current API fully satisfies the many community 
requirements in this area.  Rather than commit to indefinitely maintaining an 
API that may not turn out to be sufficient, we are going to move this new API 
into an internal package for 3.1 M7. This will give us room to evolve the API 
and come up with a stronger solution for the next release.

Comment 4 John Arthorne

2005-05-04 16:58:43 EDT

To clarify the recent changes, here is what has changed this week. All affected
classes are new in Eclipse 3.1:

1) All classes in the org.eclipse.core.resources.mapping package were moved to
org.eclipse.core.internal.resources.mapping.  

2) The class org.eclipse.ui.IContributorResourceAdapter2 in the
org.eclipse.ui.ide plugin has moved to the package org.eclipse.ui.internal.ide.

All of this code should still be considered provisional API.  Other plugins are
welcome to try it out and give feedback, as long as they understand that
breaking changes will be made to these classes in Eclipse 3.2 (minimally, they
will likely be moved back into an API package).

Comment 5 Mike Wilson

2005-05-05 13:57:19 EDT

I agree with and approve of this change. We did not manage to get an acceptable amount of external 
feedback on this new support, and given this, it is just not reasonable to declare it as set-in-stone API at 
this point.