Solving technology problems, one at a time
<= Back to previous section “Create a Branch”
<= Back to previous section “Work in the branch
<= Back to previous section “Create a Branch”
<= Back to previous section “Share the Project”
Now that you have created a project, the other people on your team should check it out from CVS. If they aren’t sure how to check out a project from CVS, have them view this tutorial then return here.
Scenario walkthrough
We’ll be following the workflow shown in the diagram below. This article will employ a scenario of two programmers, Paul and Wing, working on separate branches of the same project.
<= Back to previous section “Create the Workspace and Project”
Now that you’ve created a new project, check it into the CVS repository so your team can collaborate on it.
<= Back to previous section “Branching Strategies”
<= Back to previous section “Setting up the Eclipse Interface for CVS”
To prevent this, projects can be developed in concurrent paths, with one path being devoted to the main line of development and others set aside for testing new features or bugfixes. One line can be kept stable or close to stable, with others not yet even in testing. Several common configuration strategies are used for team collaboration on software development.
Eclipse can be used for many types of development tasks. As a result the interface is almost infinitely customizable. This can be confusing. When you first open it, you will probably see only functions related to Java development, as shown below:
You can set up multiple workspaces in CVS. This is useful for maintaining DEV, TEST and PROD environments, syncing them all to the project in the CVS repository, or it can be used to maintain differerent projects. You can also have more than one project folder in a single workspace.
