Show TOC

FusionsLocate this document in the navigation structure

Use

Design Time Repository (DTR) is capable of versioning sets of files as fusions . Sometimes it is necessary to treat a set of files as one versioned unit. In DTR such a unit (set of objects) is called a fusion. There is only one version graph for the whole fusion. When one file needs to be changed, the entire fusion is checked out from DTR. If a fusion was changed concurrently, a conflict will be reported even if the two changes affected different files of the fusion. Fusions are also a unit of change propagation: only entire fusions can be added to an activity and integrated into other workspaces, or exported to the file system.

Fusions are used to put files which belong together in a logical way under version control as a group.

Example

One example is the model-based development in the SAP NetWeaver Developer Studio. With the meta model-based tools, the developer is working on logical objects such as Web Dynpro components or service definitions. Changes are stored in different files. But for versioning, conflict detection and change propagation, it is important that you always work on the entire logical object. The solution to this problem is to declare a DTR fusion that contains all the files that belong to one logical development object (such as Web Dynpro). See Setting Up the Web Dynpro Development Component (DC) .