JBuilder already has its own CVS tool that can be called from the Team menu. 1. First add x: / jbuilderxbin to PATH, enter CVS -D: x: / cmd command line, set the path to save the file), thereby establishing a cvsroot directory. 2.Team-> Select Project VCS; Choose Use CVS 3.Team-> Place Project INTO CVS; CVS Module Properties Settings Bar; select Local in Connect Type, save it locally; then set the save path in the Repository Path (ie X: / cvspath) 4.next, select the folder 5.next that you need to save, execute the file saved. Be careful not to use other programs to call files that need to be saved. After completing the above steps, you can use the Status Browser to view the status of each file, use the commit browser to manage the files of the changes. Use Team-> Pull Project from CVS to import saved files into an empty folder. The display code has been modified locally when it is used for a while, but the code is not updated when the code is executed. The author thinks this is the bug of JBuilder's CVS tool itself, because many users have similar experiences. Here is a simple solution: delete the "CVS" file under the root directory of Project (Note: CVS will generate a CVS folder under each folder of Project, there is no need to delete, of course if you I have energy and time to delete me, and then open this Project with JBuilder. At this time, the CVS path information stored in the original project has not been used, and then only uses Team-> Place Project Into CVS to create a new CVSROOT. It is best to save the original engineering stub, because there is no such version of the new ROOT that has not been saved. This is a very soil but more effective way, but if it is not forced to be less used.
