CaliberRM® 2008 - Borland Technical Publications

CaliberRM for Eclipse
The Requirements Grid slows down when viewing a large number of requirements. It is recommended that
you use the document view instead.
The Compare Baselines report is difficult to read when using the default width. Use the Windows Client to
compare baselines.
The options to trace to Borland StarTeam, Borland Together, Borland Silk, or Mercury QC do not allow users
to create traces. Contact support to install the necessary add-ins.
When MPX is enabled and the requirement tree is refreshed by MPX events, the current cursor position is
lost. To avoid this situation, turn off MPX events on the Logon dialog box.
Navigating to non-requirement software artifacts, such as Borland StarTeam elements, from a requirement
might generate an error. It is recommended that you use the Windows Client to view these traces.
After a refresh, the requirement navigator displays requirements as locked even though they are not locked
and can be edited.
In both Eclipse 3.2 and 3.3, when you view the Traceability page of a requirement with an SCTM trace attached
to it in SCTM, the SCTM trace is not displayed. However, when you view the same requirement in CaliberRM,
the SCTM trace is displayed.
CaliberRM for Microsoft Visual Studio 2008 / Visual Studio
Team Foundation 2008
In Visual Studio 2008 integration, when you click Refresh on the CaliberRM Explorer toolbar, an empty message
opens, and the Refresh command does not work. To close the empty message, click the left button. To refresh
your CaliberRM project, either click Refresh after any requirements are opened or restart Visual Studio.
In VSTS 2008 integration, changing the direction of two traces and saving them from the Traceability
Modification dialog box results in an infinite hourglass prompt. Additionally, only one trace is displayed on
the Traceability page. Closing the requirement and opening it again displays the appropriate traces.
In Visual Studio 2008 integration, Visual Studio hangs when a CaliberRM project is removed. When multiple
baselines for the same CaliberRM project are added to CaliberRM Explorer, Visual Studio sometimes hangs
when you remove a project. This issue occurs only when requirements are opened in the Editor pane. To
avoid this issue, close all requirements before removing a project.
In Visual Studio 2008 Integration, when opening CaliberRM Explorer on Visual Studio 2008, a package load
error occurs. CaliberRM Explorer is not displayed. In VSTS 2008 Integration, when connecting to CaliberRM
Server from Team Explorer on Visual Studio 2008, the request never finishes. Both problems are caused by
a missing J# library. As a result, users must install the J# redistributable separately because Visual Studio
2008 no longer includes J#. It is recommended that you download Microsoft Visual J# ® 2.0 Redistributable
Package, Second Edition (x86) from
http://www.microsoft.com/downloads/details.aspx?FamilyId=E9D87F37-2ADC-4C32-95B3-B5E3A21BAB2C
and install it before installing Visual Studio 2008 or VSTS 2008 Integrations.
In Visual Studio Team foundation 2005 and 2008, while uninstalling CaliberRM for Team Foundation Server
(TFS Integration), the uninstaller fails to unregister the CaliberRM entry. To remove the CaliberRM entries
manually from the Microsoft Visual Studio Team Foundation Server 2005 (TFS 2005), perform the following
steps:
1. Run the command TFSReg with the /D switch before uninstalling, as the following example shows.
30 | CaliberRM 2008 Release Notes