blob: 2c97d60ddf7da82f96afea53afc9ab4f40d6106b [file]
<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
<HTML>
<HEAD>
<META HTTP-EQUIV="Content-Type" CONTENT="text/html; charset=ISO-8859-1">
<META HTTP-EQUIV="Content-Style-Type" CONTENT="text/css">
<LINK REL="STYLESHEET" HREF="../book.css" CHARSET="ISO-8859-1" TYPE="text/css">
<title>Sharing a new project using CVS</title>
<meta name="keyword" content="team">
</HEAD>
<BODY BGCOLOR="#ffffff">
<H1>Sharing a new project using CVS</H1>
<P>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.
</P>
<P>To share a new project using CVS:
</P>
<ol>
<li>In the Navigator view, select the project to be shared.</li>
<li>Select <b>Team &gt;</b> <b>Share Project...</b> from the project's
pop-up menu. The Share Project wizard opens.</li>
<li>From the list of available repository providers, choose <b>CVS</b> and click
<b>Next </b>to go to the next page. <b>(Note</b>: If there is only one repository
provider available, the first page will be skipped and next page will be displayed
automatically.)</li>
<li>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 <b>Next</b>.</li>
<li>If entering a new repository location, enter the repository information
and click <b>Next</b> when completed. <b>(Note</b>: this page is the same format
as the <a href="tasks-92.htm">Creating a CVS repository location</a> wizard.)</li>
<li>(Optional) Either choose to use the name of the local project as the remote
project name or enter another name.</li>
<li>Click <b>Finish</b> to share the project with the repository. The project
folder will be created remotely and the Synchronize view will open and allow
the committing of the project's resources. <b>(Note</b>: If the project already
exists remotely, the Synchronize view will show conflicts on any files that
exist both locally and remotely.)</li>
</ol>
<p><h4>Consequences for Linked Resources</h4>
As mentioned in <a href="../concepts/concepts-13.htm">Linked resources</a>, 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.
<p><img border="0" src="../images/ngrelc.gif" alt="Related concepts" width="159" height="27"><br>
<a href="../concepts/concepts-26.htm">Team programming with CVS</a><br>
<a href="../concepts/concepts-27b.htm">Branches</a><br>
<a href="../concepts/concepts-30.htm">Synchronizing with a CVS repository</a>
</p>
<p><img border="0" src="../images/ngrelt.gif" alt="Related tasks" width="159" height="27"><br>
<a href="tasks-117a.htm">Project checked out with another CVS tool</a><br>
<a href="tasks-96.htm">Checking out a project from a CVS repository</a><br>
<a href="tasks-103.htm">Replacing resources in the Workbench</a>
</p>
<p><img border="0" src="../images/ngrelr.gif" alt="Related reference" width="159" height="27">
<br><a href="../reference/ref-47.htm">CVS</a>
</p>
<p>&nbsp;<br>
<a href="../hglegal2003.htm"><img src="../images/ngibmcpy2003.gif" alt="Copyright IBM Corporation and others 2000, 2003" border="0" width="324" height="14"></a>
</p>
</BODY>
</HTML>