Skip to main content

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.

Jump to: navigation, search

E4/Resources/Requirements/3.7

< E4‎ | Resources‎ | Requirements
Revision as of 10:00, 22 April 2010 by Unnamed Poltroon (Talk) (New page: The purpose of the page is to capture requirements on e4 resources to be implemented in 3.7 timeframe. = New Requirements = == Team Support Registration for Linked Resources == === Prob...)

(diff) ← Older revision | Latest revision (diff) | Newer revision → (diff)

The purpose of the page is to capture requirements on e4 resources to be implemented in 3.7 timeframe.

New Requirements

Team Support Registration for Linked Resources

Problem Description

With current implementation, Team Support (Team Provider, Move/Delete Hook, Rule Factory) is defined on project level under the assumption/simplification that all resources of a project are versioned in one source repository. When using linked resources, the assumption of one repository may not be true. For example, one project may be already migrated from CVS to Git and another not. With RESTful resources coming from different sources, it is also desirable to be able to handle them in one Eclipse project instead of creating separate.

Proposal

The proposal is to allow team provider registration on the level of linked folders and implement/enable the ability to delegate functionality to the nested providers/hooks/rule factories.

Back to the top