jCVS Considerations

The jCVS client is considerably different from the typical command line interface. A project is shown graphically, and instead of commands working on a directory's contents, they typically operate on the files selected in the gui front end. The following list will attempt to point out the most obvious differences.

• Most commands now operate on selected files.

  In the command line interface, commands typically work on the current directory's contents, and in some cases, recursively down the directory tree. In jCVS, the table is turned. Since you can select individual files in the project's display, commands now typically operate on the files currently selected. In the cases where commands still operate on the entire contents of the project or a directory, the command will point that out. Otherwise, assume the command operates on the selected files.

• Output does not go to stdout.

  jCVS captures all cvs server output and displays that output in a text window. This means that (currently) you can not re-direct that output to a file. This is typically not a concern. However, if you expect the results of a command to be more than several pages of output, then you may wish to use caution, as the Java interpretter may run out of memory trying to display the results.

  It is expected that a future release will give you the option of re-directing output to a file.