Storage Mergers

org.eclipse.team.core.storageMergers

3.2

This extension point allows a plug-in to register a storage merger for specific content types. The storage merger is expected to perform a three-way merge on three input storage and write the result to an output stream. The extension point must implement the interface org.eclipse.team.core.mapping.IStorageMerger.

<!ELEMENT extension (storageMerger* , contentTypeBinding*)>

<!ATTLIST extension

point CDATA #REQUIRED

id    CDATA #IMPLIED

name  CDATA #IMPLIED>


<!ELEMENT storageMerger EMPTY>

<!ATTLIST storageMerger

id         CDATA #REQUIRED

class      CDATA #REQUIRED

extensions CDATA #IMPLIED>


<!ELEMENT contentTypeBinding EMPTY>

<!ATTLIST contentTypeBinding

contentTypeId   CDATA #REQUIRED

storageMergerId CDATA #REQUIRED>


The following is an example of a storage merger for property files (extension "properties"):

<extension point =

"org.eclipse.team.core.storageMergers"

>

<storageMerger id=

"org.eclipse.team.internal.core.merge.PropertiesStorageMerger"

class=

"org.eclipse.team.internal.core.merge.PropertiesStorageMerger"

extensions=

"properties"

/>

</extension>

The contributed class must implement org.eclipse.team.core.mapping.IStorageMerger

The Team UI plugin defines a storage merger for line oriented text files.