Notice: This Wiki is now read only and edits are no longer possible. Please see: https://gitlab.eclipse.org/eclipsefdn/helpdesk/-/wikis/Wiki-shutdown-plan for the plan.
Workspace3.7
Workspace 3.7 Development Plan draft. Some items listed below can end up in the official 3.7 component plan. Some items that can't be applied to 3.x can end up in e4.
If you are not a member of the Platform Workspace Team and you want to add your work to the plan, please follow the steps below.
- Update an appropriate section with your request/idea/issue. If no section matches your issue, add a new section.
- Find a bug in the bugzilla describing the issue and link it next to your entry.
- Place your contact details (name, bugzilla id, email) next to your item.
Remember
- Add an item to the draft plan, only if you think you can work on it.
- Adding an item to the official plan is a strong commitment!
- The Platform Workspace team reserves the right to decide what is published on the official dev plan page.
To give you an idea what is the official dev plan, see the official 3.6 component plan.
Contents
Resources
Compare Framework
Team
Mapping between Repository Providers and Linked/Virtual Folders
Currently in Eclipse, repository providers are mapped to a project. This works well in many cases but is problematic if a project contains links to resources that are coming from other repositories (e.g. Git vs. CVS).
The proposal is to provide a capability to register a repository provider (programmatically and/or via UI) for a linked resource. All team-/repository-related functionality (Team menu, File Modification Validator, Move Delete Hook, Scheduling Rules Factory) should be delegated to the registered provider/hooks.
The request has been formulated as part of initial 4.0 requirement list. See [1].
Contact: Eduard Bartsch, SAP AG