A, CVS introduction
Concurrent Versions System (Concurrent Versions System - CVS) is a conventional version control system.
CVS can be performed using the code centralized management, record all of the code change history, providing functionality developed in collaboration and support people at the same time to modify the code file.
Benefits (memory) use version control software
- Program at any time to restore to a previous point in time.
- Modify the program to achieve mutually exclusive. It enables a program can only be modified by a developer at the same time.
- Modify the program for effective management. Users can be divided into two roles administrators and programmers, only the administrator can program to freeze (Freeze) and thawing (Unfreeze), frozen program can not be modified.
- The development environment and test environment, the operating environment for effective isolation.
- Written evaluation software developers to program quality, control the progress of software development.
- Manage documents. Users can create a special folder in version control, used to store a variety of documents generated during software development.
Second, the commonly used version control software
What are commonly used version control software (focus, memory)
- Rational ClearCase (two control two): covered include the scope of ClearCase version control, build management, workspace management and process control; ClearCase support of the vast majority of existing operating system. ClearCase installation, configuration, use relatively complex, the need for team training.
- Visual SourceSafe (VSS): is a good entry-level configuration management tool. Easy to use, using the standard Windows interface. VSS provides shared branching and merging capabilities, support for team development. VSS can only run on the Windows platform, will not run on other operating systems. VSS security is not high. The user may be provided VSS folder unreadable, read, read / write, four full control authority. VSS charge, there is no limit on the number of users.
- CVS: is a great masterpiece of open-source software world, easy to use, powerful, cross-platform, supports concurrent version control, and free; their biggest regret is the lack of appropriate technical support to solve many of the problems require users to find data, or even read the source code.
Three, CVS installation and configuration
CVS Control Panel settings (focus, memory)
- 1) About page provides a CVS version of the product, and service status and other information sources.
- 2) Set CVS repository. We edit the code via IDE, will eventually be submitted to this folder.
- 3) Control Panel in the rest of the page. For general development, using the default settings.
CVS access to set permissions (to understand)
1, the administrator account: In general, to install the machine CVS Windows system administrator, also have rights CVS administrator. Change and delete []
2, the average user accounts: general user account with administrator accounts should not be so much authority.
The software loaded CVS repository (understand)
1) Open the Eclipse CVS Perspective, create a new CVS repository connection. Right-click CVS Perspective view of the area, pop-up shortcut menu, select Repository Location ... option in the New sub-menu, the relevant settings in the pop-up window.
2) back to Java view, the project will be loaded CVS repository. Right-click the project in the pop-up menu, select Team → Share Project. In the dialog box, you can select some of the information, including CVS connection, such as captions when submitted.
Proposed (Check Out)
- First of all, we need to CVS repository copy a software image to the machine's workspace, at this moment copied, and CVS code on the code is the same.
- Then, the code may be performed on the basis of this modification, CVS able to tell the difference between the two, when the submit code, fusion requires some work. This operation is called Check Out.
Code synchronization (Synchronize): If you want to native code library code consistent with the resources, you need to select Team → Synchronize with Repository.
1) update the local file (Update) For Incoming files, files on the CVS repository contains the complete code for local files, and has a new code. Right-click the file, select Update, so it will be a local file updated to a state consistent with CVS
2) submit a local file (Commit) for Outgoing files, local files contains all the code of the file on the CVS, and the new code is added, select Commit command, so files on CVS updated version costs to the latest submitted by the .
3) to avoid conflicts (Mark as Merged) If there is a conflict in the file, the system will be protected by higher safety performance. After requires developers to confirm that conflict has been ruled out, right-click the file, select Mark as Merged command, which indicate the file has been validated developers, conflicts have been avoided. After submission can be conducted with a Commit command
