jCVS Known Problems

As if I have to tell you this - this list is not necessarily complete.

• Wrappers are unimplemented.

• List updates (in the project window) are slow for large projects.

• The edit and un-edit commands are partially implemented.

  In a real cvs client, an 'edit' followed by 'unedit' could be resolved entirely locally. First, the 'E' entry in CVS/Notify is removed. Then, a backup of the file, created when 'edit' is run, is moved back into the place of the file to be sure the timestamp and contents are re-established and match 'CVS/Entries'.

• Path file separator handling still needs review.

  It appears that the decision to work with UNIX paths almost entirely throughout jCVS was a correct one. Java appears to properly handle translations, and so far the code is working well with these paths. However, the code should still be reviewed to be certain that all handling is proper.

• Minimal international support.

  Typical of an american-centric point of view, I assumed the world speaks English. Proper internional support is a must. Fortunately, you can currently set menu names and many dialog strings via the 'Properties.txt' file if you care.