JBuilder Integration for the Telelogic/Continuus CM

Object-based File Context Menu (Project View Pane)

The File Context Menu offers you up to seven different CM operations for the selected file(s), if you did choose "Use CM" in the Project Properties Dialog and the corresponding CM repository is object-based.

If you did not select that option, all menu items will be disabled; if the repository is task-based, you will see the Task-based File Context Menu.

The selected files are those you selected in the Project View Pane. Which menu items are disabled depends on the set of files selected:

file set:     disabled menu items

multiple files selected     create, diff, status, history

readonly files only     checkin, uncheckout, create, diff

writable files only     checkout

writable and readonly files     (nothing)

Which files of a multiple selection are subject of a CM command depends on the command to be executed:

CM command to execute     file subset

checkout     readonly files only

checkin, uncheckout     writable files only

Checkin

Execute a CM checkin command for the selected file(s) (single file: menu item shows the name ; multiple files: menu item shows "files"). You will be shown the filename or the list of all files and prompted for a checkin comment.
If a file does not belong to the CM repository, you'll get a message like "Status problem" shown on the right with a hint, that the file is not yet under CM control.

Checkout

Execute a CM checkout command for the selected file(s) (single file: menu item shows the name ; multiple files: menu item shows "files").
If a file does not belong to the CM repository, you'll get a message like "Status problem" shown on the right with a hint, that the file is not yet under CM control.

Uncheckout

Execute a CM delete command (with replace) for the selected file(s), so that the checked out file is replaced by its predecessor (single file: menu item shows the name ; multiple files: menu item shows "files").
If a file does not belong to the CM repository, you'll get a message like "Status problem" shown on the right with a hint, that the file is not yet under CM control.

Create

Execute a CM create command for the selected file (menu item shows the name), so that the file is added as a member of the project in the repository.

If the file already belongs to the CM repository, you'll get the message "Status problem" shown on the right.

Diff

Execute a CM diff command for the selected file (menu item shows the name). Depending on the settings in the Project Properties Dialog the result will either be a text window with the diff result in a unix-like format (like the history result shown on the right) or the dialog of the external diff tool chosen in the Project Properties.

If the file does not belong to the CM repository, you'll get a "Status problem" message shown on the right with a hint, that the file is not under CM control.

Status

Check the status of the selected file. Possible states are:

Uncontrolled
The file is not currently under the control of CM
Removed
The file has been removed from the project work area
Working
The file has been checked out and is writable.
Minor states:
- Locally writable
  The file is checked out, but still unchanged.
- Locally modified
  The file needs to be checked in
Read-Only
The file is a read-only copy of a revision.
Minor states:
- Repository similar
  The file is a copy of the latest revision
- Repository updated
  Someone posted a newer revision to the server

The result will be a message window naming the current status.

History

Execute a CM history command for the selected file (menu item shows the name). The result will be a text window with the history result (shown on the right).
If a file does not belong to the CM repository, you'll get a message like "Status problem" shown on the right with a hint, that the file is not yet under CM control.