Welcome to the readme for the CA Harvest Change Manager Plug‑in for Eclipse (CA Harvest Plug‑in for Eclipse) r6.20.2 and r7.20.2. This document contains important information you need to know before installing or using the CA Harvest Plug‑in for Eclipse with CA Harvest Change Manager (CA Harvest) r7.1 SP1 or CA Harvest r7 patch 4 with Hotfix PR6027. For information on installing CA Harvest components, see the CA Harvest r7.1 or CA Harvest r7 documentation, available from Technical Support at http://ca.com/support. Important! Two versions of the CA Harvest Plug‑in for Eclipse are distributed with this release, with each version supporting one or more specific versions of Eclipse. Use the following list to determine which version of the CA Harvest Plug‑in for Eclipse you need for your Eclipse installation:
For Eclipse 3.1 or 3.2, install the CA Harvest Plug‑in for Eclipse version 7.20.2.
For Eclipse 3.0, install the CA Harvest Plug‑in for Eclipse version 6.20.2.
Prior to releases 6.20.2 and 7.20.2, you had to use Harweb to perform Interactive Merge. In this release, you can now perform the interactive merge process using Eclipse's built-in compare and merge tool (if your server has been upgraded to CA Harvest r7.1 SP1), or you can continue to perform Interactive Merge using Harweb.
To use Eclipse's built-in compare and merge tool, ensure the Harweb preference is not enabled. Then, right-click your desired M-tag version and select Interactive Merge. The Eclipse Compare/Merge tool is displayed for the compare and merge process.
To continue using Harweb to perform Interactive Merge, enable the preference by selecting Window, Preferences, Team, CA Harvest CM, Use Harweb for Interactive Merge. Note: For both situations, an Interactive Merge process must exist on the broker/project/state. In the next major release, the option to use Harweb for Interactive Merge may not be available. In addition, third-party merge tools such as Beyond Compare, Guiffy, and so forth are not supported in this maintenance release.
This section lists the platforms supported by the CA Harvest Plug‑in for Eclipse. CA supports these platforms for the duration of their life cycle, as determined by their manufacturer, or until CA announces that we are no longer supporting them. For the latest information about supported platforms, see our web site, http://ca.com/support.
This release of the CA Harvest Plug‑in for Eclipse is supported with CA Harvest r7 patch 4 with PR6027 Hotfix (Improve Eclipse Synchronization Performance) applied to the CA Harvest server, and CA Harvest r7.1 SP1. Note: If you try to use the CA Harvest Plug‑in for Eclipse r6.20.2 and r7.20.2 with releases of CA Harvest not listed in this readme, you will encounter improper execution results when using the synchronization feature of the plug-ins.
The Eclipse Foundation's Eclipse SDK 3.2, 3.1, or 3.0 must be installed separately on the supported platforms. If your target integrated development environment (IDE) is one of the following IBM IDEs that installs Eclipse, you do not need to install a separate version of Eclipse:
IBM Rational Application Developer 6.0 or 7.0
IBM Rational Web Developer 6.0 or 7.0
IBM WebSphere Development Studio Client for iSeries 6.0
The IBM Rational Application Developer (formerly known as WebSphere Studio Application Developer) 6.0 and IBM Rational Web Developer (formerly known as WebSphere Studio Site Developer) 6.0 IDEs are also supported by Eclipse 3.0. Note: Release 7.0 of these products is now available from IBM. CA has not explicitly tested release 7.0. However, there are no known changes that would prohibit successful operation of the latest plug-ins with r7.0 of these IDEs, which are built on Eclipse 3.2.
CA Harvest Plug‑in for Eclipse r6.20.2 and r7.20.2 are not supported with IBM WebSphere Studio Application Developer (Eclipse 2.1). If you are still using this version, we recommend that you upgrade to IBM's later replacement release Rational Application Developer.
This section contains prerequisite information for installing the CA Harvest Plug‑in for Eclipse and instructions to install the plug‑in for your operating system platform. Before proceeding, ensure that you have the CA Harvest documentation available, especially the CAHarvest Change Manager Installation Guide and readme. The latest CA Harvest documentation is available from Technical Support at http://ca.com/support.
Note: If you are using CA Harvest r7.0 P4, Hotfix PR6027 must be applied to your CA Harvest server before upgrading to the CA Harvest Plug-in for Eclipse r6.20.2 or 7.20.2. Information and instructions to download the hotfix are available from https://support.ca.com. Before installing the plug‑in, you must install the CA Harvest client, Harweb, and the Eclipse SDK or one of the IBM IDEs in the System Requirements. To install CA Harvest and Eclipse components
Install the CA Harvest client on each computer where the plug‑in will be installed, according to the instructions in the CAHarvest Change Manager Installation Guide. Install Harweb on a computer that is accessible by the workstation where the plug‑in is installed. The plug‑in works with Harweb for certain functions such as interactive merge and forms management. For instructions on installing Harweb, see the CAHarvest Change Manager Installation Guide.
Install the Eclipse SDK 3.2, 3.1, or 3.0 on each computer where the plug‑in will be installed. Note: The Eclipse SDK must be downloaded from http://www.eclipse.org and installed on the target systems prior to installing the plug‑in. The SDK version of Eclipse 3.2, 3.0, or 3.1 (eclipse‑SDK‑n.x‑<platform>) must be downloaded and used, rather than the platform version (eclipse‑platform‑n.x‑<platform>). For example, Linux needs eclipse‑SDK‑3.0‑linux-gtk.tar. The Eclipse SDK 3.2, 3.1, and 3.0 includes the Eclipse Platform, Java development tools, and Plug‑in Development Environment, which contains source code, user documentation, and development documentation. Eclipse does not include a Java Runtime Environment (JRE). For the proper version of the JRE or Java Development Kit (JDK) that must be installed on your machine to run Eclipse, go to: http://wiki.eclipse.org/index.php/Eclipse_FAQs. The CA Harvest Plug‑in for Eclipse is installed using the Eclipse Update Manager, a feature provided by Eclipse. The Eclipse Update Manager is a built‑in plug‑in installation and update manager that simplifies the installation process and lets you manage various plug‑in instances. For details on managing your configuration, see the Eclipse help.
To install the CA Harvest Plug‑in for Eclipse for CA Harvest r7.1 SP1 or CA Harvest r7 P4 (with hotfix PR6027), use the Update Manager in Eclipse. To install the CA Harvest Plug-in for use with Eclipse 3.1 or 3.2
In Eclipse, select Help, Software Updates, Find and Install. The installation wizard opens.
Select Search for new features to install and click Next.
Click New Remote Site. The New Remote Site dialog opens.
When you perform a Switch Package operation and move files from one package to another, the default package settings at the project level do not change. The package properties are inherited from the parent project. To change the default settings for the package, you must use the Edit Harvest Context option.
When using the Firefox-based embedded SWT browser on Linux, Eclipse does not inherit the proxy settings from the Firefox preferences. Eclipse has documented this issue under the following bug report: https://bugs.eclipse.org/bugs/show_bug.cgi?id=82295. As a workaround for those customers using HTTP proxies on Linux, switch to the Mozilla browser until Eclipse resolves this issue. To switch to the Mozilla browser
Open the Eclipse Workbench.
On the Window menu, click Preferences. The Preferences dialog appears.
In the tree on the left, expand General and click Web Browser. The Web Browsers page appears.
Under External Web browsers, add the information for the Mozilla browser and click OK. When Harweb is started, the Mozilla browser is opened.
When using CA Harvest r7.0 P4 with the CA Harvest Plug‑in for Eclipse r6.20.2 and r7.20.2 and trying to perform an Undo Checkout of a branch version in which the parent trunk has been previously removed from the source line (that is, the Remove Item process has been performed on the file), you will receive an error indicating that the operation cannot be completed and the log file indicates that the file has not been checked out. As a workaround, perform a Delete Version on the deleted version (that is, the latest trunk version) to bring the file back into the code line. You can then perform an Undo Checkout successfully. The Remove Item process can then be performed and the code deleted.