1.0 Introduction
2.0 Known problems and limitations
2.1
"extssh" is not a supported command line method
2.2
Connection cannot be found after initially missing
2.3 CVS meta-folders appear in some cases
2.4 "Received broken pipe signal" error from server
2.5
"Terminated with fatal signal 10" error from server
2.6
Team > Update does not indicate that there are outgoing changes
2.7
Synchronize view "Mark as Merged" has surprising behavior with
respect to modes
2.8
Team > Commit on an unchanged file does not update decorator
2.9
Change ASCII/Binary Properties not available for unadded files
2.10
Error updating incoming directory additions with pruning turned off
2.11 "Remove from View" in Synchronize view does not exclude resources
from view actions
2.12
Ctrl-S does not save in Synchronize view and CVS compare views
2.13
CVS automatically prunes empty directories
2.14 ClassCastException on attempt to replace directory with file
2.15
Still prompted if delete unmanaged preference turned off
2.16
Hidden CVS/ folders get copied when copying folders from one project to
another
2.17 Cached authorization information lost when workspace is upgraded
2.18 "Unknown response" error using ext connection method
2.19 No way to update folder excluding subfolders
This contains information on known problems and limitations for team programming with CVS.
Since the "extssh" connection method is not a supported command line method, you cannot use the command line tool when a project uses this method. Instead, use the WebSphere Studio supported "ext" method and set the appropriate environment variables so that the command line tool will work.
If a connection initially fails due to a network problem, the connection may continue to fail even when the network problem is fixed. In order to establish the connection you must exit and restart WebSphere Studio.
There are some cases where setting folders as team private won't hide them from the UI as the user would expect.
WebSphere Studio sometime performs multiple commands within a single connection to the server. This may cause problems with CVS servers that are running server scripts in response to certain commands.
There is a bug in the CVS server related to some compression levels. If you get this error, changing the compression level on the CVS preference page may help.
The Team > Update command will load all remote changes into your local working copy. If you are using Team > Update and you want to see which files have outgoing changes, open the CVS console before performing the update. The console will show the results of the update (which files had mergeable conflicts, which ones had unmergeable conflicts and which ones had outgoing changes). Warning: Only use Team > Update if you know CVS. If there are "real" conflicts (i.e., those that affect the same line of a file) then CVS will add markup to the file during the update. Resolving these conflicts in this manner is not pleasant.
When you Mark as Merged, if it's your only incoming change and you are in the incoming mode, the sync view becomes empty. On the surface it looks like the change is gone. However, your change will appear in outgoing mode.
If you perform a Team > Commit on a file that has been modified but whose contents match the contents of the file on the server, the file will remain on outgoing change. To correct the problem, either perform a Team > Update or use the Synchronize view to commit.
The Change ASCII/Binary Properties menu item is only enabled for files and folders that are under CVS control. If you want to set the keyword substitution mode for a new file, you will need to add it to version control first.
If pruning is turned off and a project has incoming nested folder additions that do not contain any files, performing an update in the Synchronize view will result in an error (cannot create folder). The workaround is to perform a Team > Update which will bring in the directories.
If you remove one or more resources from the Synchronize view using the Remove from View menu item, these resources will no longer appear but they will still be included in any performed operations (Update, Commit, etc.)
Ctrl-S does not perform a save in the workspace resource editor in the Synchronize view. Instead, use the popup menu and choose Save.
By default, empty directories will be pruned on checkout and update. This is desirable in most cases as directories on a CVS server are never deleted. However, if this causes problems, there is a CVS preference to disable auto-pruning.
Performing the following steps will result in the above exception:
The workaround is to commit the folder deletion before creating the new file.
If the "delete unmanaged resources on replace" preference has been disabled on the Team > CVS preference page and a Team > Replace With operation is performed on a project that has one unmanaged resource and no other outgoing changes, the user is prompted to overwrite local changes even though the operation will not overwrite the unmanaged resource.
If you copy a folder that is under CVS control to a folder that is not, the CVS/
folders (usually not shown) will be copied as well. This can cause problems if
the target project is under CVS control and you try to add the moved folder to
CVS control. The workaround is to manually delete the CVS/
subdirectories using the file system browser, or disconnect the source project
from CVS control before copying the folders.
The platform's internal authorization database file format has changed. Because of this, authorization information cached with a workspace created with an earlier version of WebSphere Studio will be unusable, and the user will need to re-authenticate.
There are a few situations that can result in an "Unknown response" error messages when using the ext connection method. One situation involves using an external communications client (for example,. rsh or ssh) that adds CRs to the communications channel. Another involves WebSphere Studio not properly reading the stderr output of the external communications tool
There is currently no way in WebSphere Studio to run a non-recursive update on a folder (that is, there is nothing equivalent to the cvs -l option).
Return to the main readme file
(C) Copyright IBM Corporation 2000, 2003. All Rights Reserved.