My web server - Version Management Now you can mark the current
Version Management Now you can mark the current project state as Version 1. It is this function that makes a CVS interesting even for a sole developer. Without a CVS, Eclipse cannot manage project versions. Select all Java files from the DukeSpeaks project. Apply the Team > Tag as Version context function to this selection. Then enter the version number. You should apply this function only to files that you have previously synchronized with Team > Commit. In this case, however, you might just as well apply the function on the project itself, and thus on all source files in the project. In principle, working on a repository-based project is no different from working on a private project. All modifications are applied to the local resources without accessing the repository. The local resources are synchronized with the resources in the repository only when you apply the Team > Commit context function to selected resources. Resources that were changed since the last synchronization with the repository are prefixed with a > character in the explorer. Working in a Team When several developers work on the same project, not only may the local version be newer than the central version, but the reverse situation is also possible if resources were changed and committed by other team members. You should always first import the changes made by other team members into your local project before committing your changes to the repository. You can do this import with the Team > Update function. In cases where several team members work simultaneously with the same resource, it may happen that the resource gets changed by more than one team member. Here, we differentiate between three conflict types: . Case 1: No conflict. Either the local or the central copy of the file was changed, but not both. . Case 2: A conflict that can be resolved by automatic merging. This works only if the same lines of code have not been modified in both the local and the central version. . Case 3: A conflict that can only be resolved manually. Here the resource contains lines that were modified in both the local and the central version. The various functions for synchronization of resources react differently under these different conflict cases. The Update function, for example, replaces the local copy in any case with the central copy. However, in cases 2 and 3, the previous local version is saved under a modified name as a backup. In case 3, the function adds comments to the file to make the conflicts visible. The Synchronize function, in contrast, opens the Compare Editor (see Figure 7.3). There is even a specific Team Synchronizing Perspective that can be opened in the usual way: 1. After you press the Synchronize CVS tool button in the Synchronize View, the type of conflict is shown here for each resource. You may then apply an appropriate context function to a selected resource. With Override and Update you can resolve conflict cases of types 1 and 2. Type 3 cases, however, need manual treatment. For this purpose you must invoke the Open in Compare Editor function (Figure 7.3). Here, you can apply the necessary changes. 133 Advanced Topics of Project Development
If hosting is cheap, it doesn’t need to be second-rate. Try us if you don’t believe cheap web hosting we have 30 days money back guarantee.