| <!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN"><html lang="en"> |
| <HEAD> |
| |
| <meta name="copyright" content="Copyright (c) IBM Corporation and others 2000, 2011. This page is made available under license. For full details see the LEGAL in the documentation book that contains this page." > |
| |
| <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 your workspace setup using Project Sets</title> |
| <meta name="keyword" content="team"> |
| <script language="JavaScript" src="PLUGINS_ROOT/org.eclipse.help/livehelp.js" type="text/javascript"> </script> |
| </HEAD> |
| |
| <BODY BGCOLOR="#ffffff"> |
| <H1 CLASS="Head"> Sharing your workspace setup using Project Sets</H1> |
| <P CLASS="Para">Your workspace setup may consist of several projects from one |
| or more repositories. Once you have setup your workspace, you can share it with |
| others by exporting a Team Project Set. A project set is a text file that contains |
| a pointer to each of the projects contained in the project set.When a project |
| set is imported, these pointers are used to fetch the projects from the repository. |
| Project sets can include any projects that are mapped to repository tooling |
| that provides support for them, such as CVS. To export a project set:</P> |
| <ol> |
| <li>Setup your workspace with all the projects you want to work on by checking |
| them out of CVS or obtaining them in any manner appropriate for the repository |
| tooling you are using.</li> |
| <li>From the <strong>File</strong> menu, choose <strong>Export</strong>. The |
| <a class="command-link" href='javascript:executeCommand("org.eclipse.ui.file.export")'> |
| <img src="PLUGINS_ROOT/org.eclipse.help/command_link.png" alt="command link"> |
| Export dialog</a> will open.</li> |
| <li>In the Export dialog, choose <b>Team > Team Project Set</b> and click <strong>Next</strong>. |
| The dialog will now display all the projects that are eligible for export.</li> |
| <li>Check the projects you wish to include in the project set. Either browse |
| for or type in the name of the file where you wish to save the project set |
| and then click <strong>Finish</strong>.</li> |
| </ol> |
| <P CLASS="Para">Now you have created a project set file. You can now share this |
| file with others or use it yourself to recreate your workspace. To Import a |
| project set:</P> |
| <ol> |
| <li>From the <strong>File</strong> menu, choose <strong>Import</strong>. This |
| will open the |
| <a class="command-link" href='javascript:executeCommand("org.eclipse.ui.file.import")'> |
| <img src="PLUGINS_ROOT/org.eclipse.help/command_link.png" alt="command link"> |
| Import dialog</a>.</li> |
| <li>In the Import dialog, choose <b>Team > Team Project Set</b> and click <strong>Next</strong>.</li> |
| <li>Browse for or type in the name of the file containing the project set and |
| click Finish.</li> |
| <li>The projects contained in the project set will be fetched from the repository.</li> |
| </ol> |
| <P CLASS="Para">For CVS, you will be prompted to provide the authentication information |
| (user name and password) for the repository as it is not included in the project |
| set. </P> |
| <P CLASS="Para"><b>Specify Repository Information dialog</b></P> |
| <P CLASS="Para">When the project set contains only partial repository information |
| (not all locations are known) the Specify Repository Information window is displayed offering three options for Repository locations:</P> |
| <ol> |
| <li>Use the original location that is displayed in the first row of the Repository location column drop down list.</li> |
| <li>Click <b>OK</b> to choose a known repository location from the same drop down list (default).</li> |
| <li>Create a new repository location by clicking the <b>Create Location</b> button.</li> |
| </ol> |
| <P CLASS="Para">The user can fully configure the repository location, specify a user name, and change the connection method if required. For example, a project set file containing extssh connections can be used by a non-committer as they can reconfigure the repository location connection method on import to a pserver.</P> |
| <p><img src="../images/cvs-specify-repository.png" alt="Repositories configuration dialog"></p> |
| |
| <p><img border="0" src="../images/ngrelc.png" alt="Related concepts" ><br> |
| <a href="../concepts/concepts-26.htm">Team programming with CVS</a><br> |
| <a href="../concepts/concepts-27c.htm">CVS Repositories</a> |
| </p> |
| |
| <p><img border="0" src="../images/ngrelt.png" alt="Related tasks" ><br> |
| <a href="tasks-96.htm">Checking out a project from a CVS repository</a><br> |
| <a href="tasks-96a.htm">Checking out a module from a CVS repository</a><br> |
| <a href="tasks-92.htm">Creating a CVS repository location</a><br> |
| <a href="tasks-117.htm">Sharing a new project using CVS</a></p> |
| |
| <p><img border="0" src="../images/ngrelr.png" alt="Related references" ><br> |
| <a href="../reference/ref-47.htm">CVS</a><br> |
| <a href="../reference/ref-32.htm">CVS Repositories view</a><br> |
| <a href="../reference/ref-40a.htm">CVS Checkout wizard</a></p> |
| |
| |
| </BODY> |
| </HTML> |
