Sharing a new project using CVS
There are several scenarios that can occur when sharing a project using CVS.
The most common scenario is sharing a new project using CVS when the project
does not already exist remotely.
To share a new project using CVS:
- In one of the navigation views, select the project to be shared.
- Select Team > Share Project... from the project's pop-up
menu. The Share Project wizard opens.
- From the list of available repository providers, choose CVS and click
Next to go to the next page. (Note: If CVS is not present in
the list, it may be disabled. Clicking on the Show All Wizards
button should make it visible. Also note that if there is only repository provider registered
for your workspace, you will automatically bypass this step entirely.)
- Select the target repository from the list of known repositories or, if
the target repository is not in this list, choose to create a new repository
location and click Next.
- If entering a new repository location, enter the repository information
and click Next when completed. (Note: this page is the same
format as the Creating a CVS repository location
- Either choose to use the name of the local project as the remote project
name or enter another name and click Next.
- The final page shows you the resources of the new project as outgoing additions.
You can choose to commit or ignore resources from this page. (Note:
If the project already exists remotely, the page will show conflicts on any
files that exist both locally and remotely. Only those files whose contents
do not match are shown.)
- Click Finish to share the project with the repository. You will be
prompted to commit any resources in the new project that have not yet been
committed or ignored. Choosing to do so will run the commit operation in the
Consequences for Linked Resources
As mentioned in Linked resources, different
providers may handle linked resources differently. For Team CVS, linked resources
are allowed but ignored. Specifically, projects which contain linked resources can be shared with CVS,
but the linked resources themselves cannot be version controlled.
Team programming with CVS
Synchronizing with a CVS repository
Project checked out with another CVS tool
Checking out a project from a CVS repository
Replacing resources in the Workbench