RE: [cdt-dev] First gotcha with add/exclude children of FFS

["Michael Valenta" <eclipsemfv@xxxxxxxxx>]

Doug et al,

Szymon is really the person you want to bug on this but I'll throw in my 2 cents ;-)  First, I have to say that a solution at the IResource level (e.g. using linked resources and the new hidden folder support) is infinitely better from a repository provider perspective than an EFS based solution.  You may not get all the Team support you want at the IResource level but a solution at the EFS level would certainly break the existing CVS client since the CVS client isn't EFS aware to any great extent. For instance, if you tried to hide a folder using EFS, the CVS client would probably try and recreate it the next time you performed a Team>Update. It is also important to note that the Platform does not provide all the hooks required by repository providers and I know of at least one provider that has resorted to using it's own EFS implementation under projects that are mapped to that provider to get the capabilities it requires. I think it is important that tooling in Eclipse stick to using the IResource layer as the layer they operate on and let the repository provider (or any other tooling whose responsibility it is to manage the available files) control the underlying file system. If there are shortcomings or enhancements required then you should push to get them in at the IResource level.

As for the current state of Team support for linked resources, I think the best approach is to enumerate some specific scenarios of how you see linked resources and exclusions working with descriptions of what you need to do today to get Team support and what you would like to see. It is also important to know if you expect all the links to come from the same repository (or at least repository type) or whether a project could contain content from different repository types (obviously the later would be more difficult to accommodate than the former).

Hope this helps,
Michael