The ClearTeam Explorer (CTE) plugin for Eclipse allows developers to work in a ClearCase (CC) controlled environment. ClearCase affords an activity-based way of tracking changes in a code base that allows the user to keep track of their work via activity-managed change sets. The ClearTeam Explorer, when installed as a plugin to the Eclipse workbench, allows you to keep your activities organized when you are using ClearCase UCM.
We will assume that the ClearCase environment is one that has been set up with ClearCase UCM project and components by your CC admin. Also under assumption is that the development tool is Eclipse with the ClearTeam Explorer IDE plugins installed.
The scope of this discussion is to describe one or two ways you can join projects so that you can start contributing!
The ClearTeam Explorer plugin for Eclipse allows developers to work in a ClearCase controlled environment. ClearCase/UCM affords an activity-based way of tracking changes in a code base that allows you to keep track of work. Each artifact version created is added to the current activity change set. The ClearTeam Explorer offers a few ways to visualize your activities with their change sets. These visualizations are a very useful aid in keeping work organized.
This blog has been produced to show how to install IBM DB2 v10.5 and IBM Data Studio then how to create and configure a DB2 database for use with IBM ClearQuest.
Note: This has been written assuming that the reader does not need to be guided through the default install process.
In my previous blog post, I presented a simple Perl application that addressed the tedious and difficult task one encounters when importing data into ClearQuest; that is, determining how to define the data types of fields within a ClearQuest record. If the data types are defined incorrectly, the import of data will fail because of a type mismatch and you will need to modify your ClearQuest schema to correct the issue.
One of the difficult tasks in performing an import of external data into a ClearQuest database is determining how to define the data type of a field within a ClearQuest record. If you define it incorrectly, the import of data will fail because of a type mismatch and you will need to modify your ClearQuest schema to correct the issue.