ReadMe for Borland Connect – Subversion sample connector

• Version: @Connect_buildnumber.
• Last Updated: September 12, 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 Subversion Connector for Borland Connect.  They must be copied to the root folder of the Borland Connect installation for the Subversion connector to work correctly.

Version 1.7.11 of the SVNKit can be downloaded from (http://svnkit.com/download.php ). The below files are in the lib folder of the archive.

• sequence-library-1.0.2.jar
• sqljet-1.1.8.jar
• svnkit-1.7.11

The SVNConnector.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 Subversion URL to connect to.

Known Limitations/Issues

• The SVN Connector doesn’t support performing a move/rename and a content change in the same revision.  Therefore, multiple revisions will be created for a ChangeSet having a single change indicating a file was renamed/moved and content updated.
• The SVN connector does not support impersonation.  As such, changes synchronized from the Borland Hub into SVN will show the Author as the administrative user specified in the configuration file.  However, since Borland Hub does support impersonation, the changes from SVN into Borland Hub will show the Author as the user that made the edit in SVN as long as that user’s full name exists in Borland Hub.
• The SVN Connector doesn’t identify when a move/rename is not accompanied by a content change.  Therefore, rename/move Changes from SVN will also result in a content update in Borland Hub.
• Subversion 1.8.1 and possibly other prior versions have a problem with handling files and folders containing a space.  This problem was fixed in Subversion 1.8.3.
• A single changeSet from Borland Hub may result in multiple ChangeSets in Subversion due to the requirement that each move and rename operation creates its own ChangeSet.
• The SVN 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 SVN 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.