Borland® StarTeam® 2006 Release 2 Eclipse Client Release Notes

Last updated: June 21, 2007

Welcome to the Borland StarTeam 2006 Release 2 Eclipse Client!

This file contains important information regarding this release that may not appear in online help. Please read this file in its entirety prior to using the application and before contacting Borland Product Support.

For an overview of the new features in this release, see the What's New section below.

What's New

This release provides the following new features and enhancements:

• Compatibility with Eclipse 3.3.
• In combination with Java 1.6, Windows Vista is also supported.
• The StarTeam Synchronization perspective and the Synchronization and File views have been removed. You can now use the Team context menu commands available throughout the Eclipse UI to perform actions on files and folders under StarTeam control.
• Asynchronous Access to StarTeam Server:
• You can run check in and check out operations and refresh views in the background keeping the Eclipse UI completely responsive. This prevents freeze-up on time-consuming network calls or server unavailability. These jobs can also run in parallel as long as they target different server configurations. If background operations running in jobs communicate with the same server configuration, they are queued in the order in which they were scheduled.
• When disconnected from a StarTeam server configuration:
• The UI stays responsive enabling you to work with other connected server configurations. You can open several connections to server configurations in the Server Explorer simultaneously.
• You can reconnect to the disconnected server configuration on-the-fly using the Server Explorer context menu Refresh command.
• This release now provides only the standard Eclipse Synchronization with all of its benefits such as, consistently updating what items to synchronize in the background.
• Name refactoring is more instant. If you have a colliding change, the UI displays instant feedback.
• You can link and unlink views to or from the selection mechanism. This enhancement gives you more flexibility to navigate in the workbench without having the views refresh each time and determine manually when to show related repository contents in views.
• This release supports the generic StarTeam History view.
• This release provides more flexible mapping of repository folders to workspace folders using preferences (Preferences dialog box) and potential project preferences that you can check in and share across teams. This mapping flexibility allows you to change the naming of local folders taken from either the human-readable names of StarTeam folders or their path fragments.
  The Check Out As Project wizard also displays a Mapping page where you can specify folder mapping during a check out operation. During the check out process, newly-created projects have workspace folders created with folder names applied according to the mapping settings made in the wizard.
  

• You can now enable the Quick Diff preference in text editors to indicate differences from the latest StarTeam revision of the opened file.
  
• StarTeamMPX now behaves as if working in the StarTeam Cross-Platform Client by refreshing items views on server content changes. The Cache Agent is fully supported by all check out operations (including Bulk Check Out), and you can also choose MPX Profiles in the Properties dialog box for a selected server configuration from the Server Explorer.

• You can quickly enable or disable this version of the client in the Preferences dialog box. By default, the client is automatically enabled.
• You can export a set of team project sets in Eclipse, that includes all the needed StarTeam IDs, the original server description, and the host and port information. Users importing a set of team project sets including StarTeam information can choose to change the IP addresses on-the-fly. If a user exported team project sets on one machine using internal IP addresses, the user importing may choose to override those with host names and addresses permeable through the firewall.
• This release supports updated label decorations displayed in the Eclipse Explorers to better reflect the various status states of resources. In addition to differentiation by direction such as, outgoing, incoming, and conflicting, the type-like addition, deletion, or change is also represented by the decorations. Review the StarTeam Label Decorations preference page (Preferences dialog box) for meanings of the label decorations.
• Improvements to the Check in/Check out dialog boxes:
• There are no longer two sets of Team context menu commands for Check In and Check Out with dialog boxes separating between forcing and non-forcing actions. You can opt to overwrite incoming or outgoing conflicting changes in the Check In and Check Out dialog boxes by marking the Force check-in and Force check-out options provided.
• The Check In dialog box processes not-in-view files (additions) or modified files (changes) with toolbar buttons (Additions only and Changes only) in the Changes area of the dialog box. You can selectively decide whether to check-in additions or changes by applying the appropriate toolbar button.
• Similar to the Check Out dialog box, the Check Out As Project wizard provides a page with all the check out options, such as lock status, enabling you to verify and optionally override settings made in the StarTeam preference pages (Preferences dialog box).

• The Exclude page of the New Project wizard includes folder exclusion options. For example, you may want to use this option to exclude status data from other version control systems like Subversion (.svn) or CVS (CVS).
• Addition of the StarTeam Console view. The Console allows you to monitor network commands and reports performance and errors similar to the console output of the StarTeam Cross-Platform Client's command-line -netmon argument. An additional StarTeam Console preference page (Preferences dialog box) allows you to customize the Console.
• Custom alternate property editors (APEs) from StarTeam 2005, StarTeam 2005 Release 2, and StarTeam 2006 are supported.

System Requirements

Following are the system requirements for installing and running this client.

Note: This release of the client is built with and supports Java version 1.5.0_09.

NOTE: It is strongly recommended that the Java memory allocation heap be increased when using this product. This setting is specified using the Java commands (-vmargs) -Xms and Xmx. Determining the proper settings will depend on the amount of physical memory available. Significant performance improvement will be recognized by utilizing greater amounts of memory. However, large heaps should be avoided if there is insufficient physical memory to avoid paging. For additional information regarding memory heap settings please refer to Eclipse.org, IBM.com and Java.Sun.com.

If a previous version of this product is installed on the target computer it should be uninstalled or disabled prior to installing this version.

Top

Uninstalling StarTeam Edition for Eclipse 2005 Release 2

Before installing this release, it is recommended that you disable or uninstall StarTeam Edition for Eclipse 2005 Release 2. Borland recommends this step to avoid confusion between the menu options offered between the two clients.

To uninstall StarTeam Edition for Eclipse 2005 Release 2

1. Run the StarTeam Edition for Eclipse 2005 Release 2 uninstall program.
2. Follow the on-screen instructions provided by the wizard.

To disable StarTeam Edition for Eclipse 2005 Release 2

1. Choose Help > Software Updates > Manage Configuration from the Eclipse main menu. The Product Configuration dialog box opens.
2. Select <Drive Letter>:\Borland\StarTeamEC\Eclipse from the list on the left of the dialog box.
3. Select Disable from the Available Tasks list.
4. In the resulting dialog box, click OK to accept the changes.
5. Restart Eclipse.

Tip: You can later reenable StarTeam Edition for Eclipse 2005 Release 2 by following the steps above and choosing Enable from the Available Tasks list in the Product Configuration dialog box.

Uninstalling the StarTeam Eclipse client in Together 2006 Release 2

An older version of the StarTeam Eclipse client is installed with Together 2006 Release 2, you must uninstall the older version of the client before installing the StarTeam 2006 Release 2 Client.

To uninstall the older StarTeam Eclipse client installed with Together 2006 Release 2

1. Run the Together 2006 Release 2 uninstall program.
2. Select Uninstalling specific features.
3. Choose to uninstall the StarTeam client/integration.

Top

Installation

You can install this release by downloading the installation file directly from the Borland download site at http://www.borland.com/downloads/download_starteam.html. Click the StarTeam 2006 & 2005 Rel 2 Integrations link to download this release. Be sure to uninstall any older versions of the StarTeam Eclipse client before installing the StarTeam 2006 Release 2 Eclipse Client.

Note: You must have either Eclipse 3.2.2 or 3.3 installed before proceeding with the installation of the StarTeam Eclipse client.

To install this release of the StarTeam Eclipse client

1. Close all running applications after saving all modified files.
2. Launch the executable installation file. You can download the installation file from the Borland download site http://www.borland.com/downloads/download_starteam.html.
3. Follow the on-screen installation instructions provided by the install wizard.

Top

Product Interoperability

• The StarTeam Eclipse and StarTeam Cross-Platform clients do not share the same file status information. Therefore, if you set up your projects in the Cross-Platform and StarTeam Eclipse clients to point to the same local folder structure, you should not expect the two clients to display the same file status information. In the Cross-Platform client, files may obtain an "unknown" status. This status requires you to use the Update Status command to see the actual status of the files. The same is true for the StarTeam Eclipse client. In this case, however, you need to use the Refresh Status command to see the correct file status. You should also be aware that the StarTeam Eclipse client may indicate "bi-directional" changes even if there are only incoming or outgoing changes for the files. However, performing the manual steps described here enables you to use the two clients in parallel.

• Borland Caliber DefineIT 2006 is written for use with Eclipse 3.1.1 and the StarTeam 2006 Release 2 Eclipse Client is written for Eclipse 3.2.2 and 3.3. As a result, Borland has performed very limited testing of these products together. While no issues were found, full support of this configuration is not possible and any issues encountered will be considered for repair in future versions of these products.
• This release of the StarTeam Eclipse client was tested on Eclipse 3.2.2 with Rational Application Developer 7.0, Together 2006 Release 2, and JBuilder 2007. While the tests were limited, no problems in using this version of the StarTeam Eclipse client with any of these products has been found. Since an older version of the StarTeam Eclipse client is installed with Together 2006 Release 2, you must uninstall the older version of the client before installing the StarTeam 2006 Release 2 Client. See Uninstalling StarTeam Edition for Eclipse 2005 Release 2 for more information.

Top

Known Issues

The following are known issues in this release:

• If your monitor's display appearance is set to the Windows Classic theme, filter combo boxes display incorrectly (too narrow) in the Eclipse UI. The workaround is to use the Windows XP theme. To change this setting, select Display from the Windows Control Panel. The theme is set on the Appearance tab. This is an Eclipse bug. For more information, see https://bugs.eclipse.org/bugs/show_bug.cgi?id=155159.
  
• If you enable StarTeamMPX for both the StarTeam Eclipse client and StarTeam server and you log on manually in the StarTeam Eclipse client, the client prompts you to take advantage of StarTeamMPX. If your logon is performed automatically using stored account information, the client does not display any StarTeamMPX prompts; however, a system job for StarTeamMPX is started. System jobs handle all StarTeamMPX events. These jobs are initially invisible in the Eclipse Progress view. You can display them by clicking on the drop down view menu in the Progress view, selecting Preferences, and checking the option to Show sleeping and system operations in the Progress Preferences dialog box.
• You can only overwrite files with outgoing changes using the context menu Replace with commands. For files with incoming changes only, you must first modify the files locally (to make them conflicting) before performing a force check-in.
• When you refresh the status after renaming a folder with a file added to it, the client shows the set of changes as an incoming deletion of the folder and an incoming addition of that folder and its new files. The local history is disconnected; however, this does not damage the continuity and consistency of the remote history on the server.
  
• While you can use drag-and-drop to move workspace resources, you cannot use it to share workspace resources. This is an Eclipse bug. For more information, see https://bugs.eclipse.org/bugs/show_bug.cgi?id=187972.
• When Keyword Expansion is enabled, the StarTeam Eclipse client uses the encoding specified in the StarTeam Preferences dialog box to expand the keywords in files as the files are checked-out. After check-out, any encoding changes are managed by Eclipse, not the StarTeam Eclipse client.
  
• The following procedure was left out of the Online Help.
  
  To get the local file contents replaced by the remote version and thus have keywords expanded after the project settings for keywords were changed
  
  1. Select the workspace file, and choose Replace with > Revision from the context menu.
  2. Select the latest revision. Doing so does not change the file; however any keywords in the file (such as, $Header$) are expanded.
• By default when using the Checkout as Project command, the lock status is set to Keep Current. Any other lock preferences set in the Preferences dialog box are ignored.
  

Top

Getting Help

For more information about Borland support services, please see Borland Answers, our support web site, at http://www.borland.com/us/services/support/index.html.

Top