ReadMe for Borland Connect – Git sample connector

• Version: @Connect_buildnumber
• Last Updated: September 25, 2014

Please refer to the Borland Community and Borland Connect Release Notes for further configuration instructions.

This connector requires at least build 1.0.3.45 of Borland Connect. The latest version of Borland Connect can be downloaded from Micro Focus SupportLine (http://supportline.microfocus.com).

Required Libraries

The following libraries are required to run the Git Connector for Borland Connect. They must be copied to the root folder of the Borland Connect installation for the connector to work correctly.

• Version 3.1 of the JGit library which can be downloaded from (https://github.com/eclipse/jgit/ ) - org.eclipse.jgit-3.1.<n>-r.jar.
• Version 0.1.50 of the JSch – Java Secure Channel library which can be downloaded from (http://www.jcraft.com/jsch/) – jsch-0.1.50.jar.

The GitConnector.jar from the deploy folder should be copied to the root folder of the Borland Connect installation.

Required Connection Information

In order to use this connector, you will need to collect and enter this information in the Borland Connect user interface or in the <datasource> element in the Connect.xml file:

• Name - Borland Hub option. Enter a unique name for the data source.
• Product - Borland Hub option. Select the data source product name.
• TimeOffset - Borland Hub option. Number of seconds the data source time differs from the Borland Connect process time.
• User - Enter the user name.
• Password - Enter the password for the user.
• URL - Enter the Git URL to connect to.

Known Limitations/Issues

• Git only surfaces changes to files. Therefore, when the last file in a folder is either deleted or moved from the folder, the GitConnector will also generate a Delete Folder change. If bi-directional synchronization is taking place, be sure that the connector is not in a “merge” situation – e.g. a new file in the corresponding folder in the Borland Hub has been added.
• The Git connector does not support impersonation. As such, changes synchronized from Borland Hub into Git will show the Author as the administrative user specified in the configuration file. However, since Borland Hub does support impersonation, the changes from Git into Borland Hub will show the Author as the user that made the edit in Git as long as that user’s full name exists in Borland Hub.
• A single changeSet from Borland Hub may result in multiple ChangeSets in Git due to the requirement that a move or rename cannot preceed a content change in the sameChangePackage (commit) if history of the item is to be preserved.
• The Git connector requires that the LinkMapProperty be set to Comment. In the UI this is set in the "Mapped External Type ID Property" on the Advanced tab of the Edit Type dialog. The value for the "Borland Hub External Type ID Property" must be "Name". No property mappings are supported.
• If specified, the "Project Path" for the Git connector, must have the form /Folder{/Folder}, e.g. beginning with a slash and ending with a name. In the xml, is the either the sourceRootPath or targetRootPath.