platform-vcm-home/docs/online/cvs_features2.0/cvs-faq.html

Parent Directory Parent Directory | Revision Log Revision Log | View Patch Patch

revision 1.53, Wed Apr 20 18:13:09 2005 UTC revision 1.54, Wed Apr 20 18:14:14 2005 UTC
# Line 2  Line 2 
2  <html xmlns="http://www.w3.org/1999/xhtml" xml:lang="en">  <html xmlns="http://www.w3.org/1999/xhtml" xml:lang="en">
3  <head>  <head>
4    <meta content="application/xhtml+xml; charset=utf-8"    <meta content="application/xhtml+xml; charset=utf-8"
5   http-equiv="content-type">   http-equiv="content-type" />
6    <meta content="haran" name="author">    <meta content="haran" name="author" />
7    <meta content="Windows Notepad" name="generator">    <meta content="Windows Notepad" name="generator" />
8    <link type="text/css" href="http://dev.eclipse.org/default_style.css"    <link type="text/css" href="http://dev.eclipse.org/default_style.css"
9   rel="stylesheet">   rel="stylesheet" />
10    <link title="Grey boxes stylesheet"    <link title="Grey boxes stylesheet"
11   href="http://dev.eclipse.org/viewcvs/index.cgi/%7Echeckout%7E/platform-vcm-home/layout.css"   href="http://dev.eclipse.org/viewcvs/index.cgi/%7Echeckout%7E/platform-vcm-home/layout.css"
12   type="text/css" rel="stylesheet">   type="text/css" rel="stylesheet" />
13    <link    <link
14   href="http://dev.eclipse.org/viewcvs/index.cgi/%7Echeckout%7E/platform-vcm-home/colors.css"   href="http://dev.eclipse.org/viewcvs/index.cgi/%7Echeckout%7E/platform-vcm-home/colors.css"
15   type="text/css" rel="stylesheet">   type="text/css" rel="stylesheet" />
16    <title>Eclipse Platform - CVS FAQ</title>    <title>Eclipse Platform - CVS FAQ</title>
17  </head>  </head>
18  <body>  <body>
19  <table width="100%" cellpadding="2" cellspacing="5" border="0">  <table width="100%" cellpadding="2" cellspacing="5" border="0">
20    <tbody>    <tbody>
21      <tr>      <tr>
22        <td width="72%" align="left"> <font class="indextop"> CVS</font><br>        <td width="72%" align="left"> <font class="indextop"> CVS</font><br />
23        <font class="indexsub">platform cvs support</font></td>        <font class="indexsub">platform cvs support</font></td>
24        <td width="28%"><img width="120" height="86"        <td width="28%"><img width="120" height="86"
25   src="http://dev.eclipse.org/images/Idea.jpg"></td>   src="http://dev.eclipse.org/images/Idea.jpg" /></td>
26      </tr>      </tr>
27    </tbody>    </tbody>
28  </table>  </table>
# Line 222  Line 222 
222        <li>Find the module you are interested in.</li>        <li>Find the module you are interested in.</li>
223        <li>Context Menu-&gt;Check Out As Project.</li>        <li>Context Menu-&gt;Check Out As Project.</li>
224      </ol>      </ol>
225      <br>      <br />
226  The project now exists in your workspace. </li>  The project now exists in your workspace. </li>
227    <p>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; <br>    <p>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; <br />
228    </p>    </p>
229    <li><b><a name="gettingStarted_2">How do I put a project into CVS    <li><b><a name="gettingStarted_2">How do I put a project into CVS
230  from my workspace?</a></b>  from my workspace?</a></b>
# Line 240  Line 240 
240        <li>Answer yes when prompted to add new files to version control.</li>        <li>Answer yes when prompted to add new files to version control.</li>
241        <li>Supply a release comment if you like.</li>        <li>Supply a release comment if you like.</li>
242      </ol>      </ol>
243      <br>      <br />
244  The project now exists in the repository. </li>  The project now exists in the repository. </li>
245    <p>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; <br>    <p>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; <br />
246    </p>    </p>
247    <li><b><a name="gettingStarted_3">I already have a project checked    <li><b><a name="gettingStarted_3">I already have a project checked
248  out from CVS with the command-line tool. How do I use it in Eclipse  out from CVS with the command-line tool. How do I use it in Eclipse
# Line 257  Line 257 
257        <li>The wizard should tell you that it found all the necessary        <li>The wizard should tell you that it found all the necessary
258  information. Click Finish.</li>  information. Click Finish.</li>
259      </ol>      </ol>
260      <br>      <br />
261  Eclipse has now shared the project with the CVS repository. </li>  Eclipse has now shared the project with the CVS repository. </li>
262    <p>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; </p>    <p>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; </p>
263  </ol>  </ol>
264  <br>  <br />
265  <!-- Browsing the Repository  -->  <!-- Browsing the Repository  -->
266  <h1>Browsing the Repository</h1>  <h1>Browsing the Repository</h1>
267  <ol>  <ol>
# Line 288  Line 288 
288        <li>Click "Add Selected Tags".</li>        <li>Click "Add Selected Tags".</li>
289        <li>Click "OK".</li>        <li>Click "OK".</li>
290      </ol>      </ol>
291      <br>      <br />
292  The CVS Repositories view will now display the chosen tags under the  The CVS Repositories view will now display the chosen tags under the
293  Branches and Versions categories. In addition, these tags will show up  Branches and Versions categories. In addition, these tags will show up
294  in other tag-related operations, such as "Replace With-&gt;Branch or  in other tag-related operations, such as "Replace With-&gt;Branch or
# Line 329  Line 329 
329    </li>    </li>
330    <p>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; </p>    <p>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; </p>
331  </ol>  </ol>
332  <br>  <br />
333  <!-- Server Issues  -->  <!-- Server Issues  -->
334  <h1>Server Issues</h1>  <h1>Server Issues</h1>
335  <ol>  <ol>
# Line 477  Line 477 
477        <li>create a group having full access rights to the CVSNT        <li>create a group having full access rights to the CVSNT
478  repository directory structure plus the temp folder CVSNT is using.  repository directory structure plus the temp folder CVSNT is using.
479  This is easiest if you specify a separate CVSNT temp directory such as  This is easiest if you specify a separate CVSNT temp directory such as
480  "c:\cvstemp" using the Advanced tab in the<br>  "c:\cvstemp" using the Advanced tab in the<br />
481  CVSNT control panel.&nbsp; (The default temporary directories in  CVSNT control panel.&nbsp; (The default temporary directories in
482  "C:\WINNT\TEMP" and "C:\Documents and Settings" have access  "C:\WINNT\TEMP" and "C:\Documents and Settings" have access
483  restrictions under Win2000 and WinXP).</li>  restrictions under Win2000 and WinXP).</li>
# Line 505  Line 505 
505  This should fix the problem. </li>  This should fix the problem. </li>
506    <p>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; </p>    <p>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; </p>
507  </ol>  </ol>
508  <br>  <br />
509  <!-- SSH  -->  <!-- SSH  -->
510  <h1>Using SSH with CVS</h1>  <h1>Using SSH with CVS</h1>
511  <ol>  <ol>
# Line 541  Line 541 
541        In Eclipse 3.0 and beyond, extssh does support SSH2. </p>        In Eclipse 3.0 and beyond, extssh does support SSH2. </p>
542    </li>    </li>
543    <li><a name="ssh_jcraft"></a><strong>My SSH server only support SSH2 protocol    <li><a name="ssh_jcraft"></a><strong>My SSH server only support SSH2 protocol
544      and I'm using Eclipse 2.1.x</strong> <br>      and I'm using Eclipse 2.1.x</strong> <br />
545      <br>      <br />
546      Eclipse comes with a built-in SSH connection method called 'extssh'. Prior      Eclipse comes with a built-in SSH connection method called 'extssh'. Prior
547      to Eclipse 3.0, this method only supported SSH1 servers. If your server is      to Eclipse 3.0, this method only supported SSH1 servers. If your server is
548      running SSH2 and you want to use Eclipse 2.1.x to connect to that server you      running SSH2 and you want to use Eclipse 2.1.x to connect to that server you
549      have two options: <br>      have two options: <br />
550      <ol>      <ol>
551        <li>use a command line SSH client that supports SSH2 with the 'ext' connection        <li>use a command line SSH client that supports SSH2 with the 'ext' connection
552          method <br>          method <br />
553        </li>        </li>
554        <li>download a plugin created by <a        <li>download a plugin created by <a
555   href="http://www.jcraft.com/eclipse-cvsssh2/">JCraft</a> that provides a SSH2   href="http://www.jcraft.com/eclipse-cvsssh2/">JCraft</a> that provides a SSH2
556          connection method. <br>          connection method. <br />
557        </li>        </li>
558      </ol>      </ol>
559      To use the 'ext' connection method, download and install an SSH command line      To use the 'ext' connection method, download and install an SSH command line
# Line 561  Line 561 
561      Method preference page, configure the location of the SSH executable and how      Method preference page, configure the location of the SSH executable and how
562      the executable is to be called. For the ext method to work the CVS client      the executable is to be called. For the ext method to work the CVS client
563      on your server must support the server mode. You can verify this by running      on your server must support the server mode. You can verify this by running
564      cvs --help-commands and ensure that the server command is supported.<br>      cvs --help-commands and ensure that the server command is supported.<br />
565      &nbsp; </li>      &nbsp; </li>
566    <li><b><a name="ssh_3">How do I set up public-key authentication for an external    <li><b><a name="ssh_3">How do I set up public-key authentication for an external
567      SSH client?</a></b>      SSH client?</a></b>
# Line 575  Line 575 
575          public key into the file <code>/home/user/.ssh/authorized_keys</code>.</li>          public key into the file <code>/home/user/.ssh/authorized_keys</code>.</li>
576      </ol>      </ol>
577    </li>    </li>
578    <br>    <br />
579    <li><b><a name="ssh_4">When I try to connect using SSH, it tells me "Could not    <li><b><a name="ssh_4">When I try to connect using SSH, it tells me "Could not
580      chdir to home directory /home/user/myname". What did I do wrong?</a></b>      chdir to home directory /home/user/myname". What did I do wrong?</a></b>
581      <p>This often happens when using SourceForge projects for the first time,      <p>This often happens when using SourceForge projects for the first time,
# Line 594  Line 594 
594        Try using another SSH client such as Putty or <a        Try using another SSH client such as Putty or <a
595   href="http://www.networksimplicity.com/openssh/">OpenSSH</a>. </p>   href="http://www.networksimplicity.com/openssh/">OpenSSH</a>. </p>
596    </li>    </li>
597    <li><a name="ssh_6"><strong>I can't get keys generated using Putty to work with Eclipse</strong></a></li>    <li><a name="ssh_6"><strong>I can't get keys generated using Putty to work with
598        Eclipse</strong></a></li>
599    <p>Putty's private key is encrypted by AES, but JCE (Java Crtptgraphy Extension)    <p>Putty's private key is encrypted by AES, but JCE (Java Crtptgraphy Extension)
600      included in J2SE 1.4.x does not support AES. So, at present time, there is      included in J2SE 1.4.x does not support AES. So, at present time, there is
601      no plan to support it. Of course, JSch (the SSH2 client used in Eclipse) may      no plan to support it. Of course, JSch (the SSH2 client used in Eclipse) may
602      support Putty's key by using the latest J2SE in the near future, but Eclipse      support Putty's key by using the latest J2SE in the near future, but Eclipse
603      3.0/3.1 will not be able to use it because they must run on J2SE 1.4.0.</p>      3.0/3.1 will not be able to use it because they must run on J2SE 1.4.0. This
604        is explained more in bug <a href="https://bugs.eclipse.org/bugs/show_bug.cgi?id=84281">https://bugs.eclipse.org/bugs/show_bug.cgi?id=84281</a>.</p>
605  </ol>  </ol>
606  <br>  <br />
607  <!-- Upgrading from Eclipse 1.0 -->  <!-- Upgrading from Eclipse 1.0 -->
608  <h1>Upgrading from Eclipse 1.0</h1>  <h1>Upgrading from Eclipse 1.0</h1>
609  <ol>  <ol>
# Line 727  Line 729 
729    </li>    </li>
730    <p>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; </p>    <p>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; </p>
731  </ol>  </ol>
732  <br>  <br />
733  <!-- Using Eclipse and CVS for Java Development -->  <!-- Using Eclipse and CVS for Java Development -->
734  <h1>Using Eclipse and CVS for Java Development</h1>  <h1>Using Eclipse and CVS for Java Development</h1>
735  <ol>  <ol>
# Line 781  Line 783 
783  level projects as subfolders of the checked out folder stucture. The  level projects as subfolders of the checked out folder stucture. The
784  steps to get this to work for the above example are:  steps to get this to work for the above example are:
785          <ol>          <ol>
786            <li>Add the following two lines to the CVSROOT/modules file<br>            <li>Add the following two lines to the CVSROOT/modules file<br />
787  test &amp;test<br>  test &amp;test<br />
788  MyProject &amp;test </li>  MyProject &amp;test </li>
789            <li>In the CVS Repositories View, select the modules with the            <li>In the CVS Repositories View, select the modules with the
790  name matching the one defined in the CVSROOT/modules file (Note that in  name matching the one defined in the CVSROOT/modules file (Note that in
# Line 859  Line 861 
861    </li>    </li>
862    <p>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; </p>    <p>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; </p>
863  </ol>  </ol>
864  <br>  <br />
865  <!-- Compatibility Between CVS Command-line Client and Eclipse -->  <!-- Compatibility Between CVS Command-line Client and Eclipse -->
866  <h1>Compatibility Between CVS Command-line Client and Eclipse</h1>  <h1>Compatibility Between CVS Command-line Client and Eclipse</h1>
867  <ol>  <ol>
# Line 970  Line 972 
972    </li>    </li>
973    <p>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; </p>    <p>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; </p>
974  </ol>  </ol>
975  <br>  <br />
976  <!-- Working with Patches -->  <!-- Working with Patches -->
977  <h1>Working with Patches</h1>  <h1>Working with Patches</h1>
978  <ol>  <ol>
# Line 1006  Line 1008 
1008    </li>    </li>
1009    <p>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; </p>    <p>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; </p>
1010  </ol>  </ol>
1011  <br>  <br />
1012  <!-- Linux -->  <!-- Linux -->
1013  <h1>Linux Issues</h1>  <h1>Linux Issues</h1>
1014  <ol>  <ol>
# Line 1023  Line 1025 
1025      <p>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; </p>      <p>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; </p>
1026      <p>The problem may be the encoding in /etc/sysconfig/i18n file. If      <p>The problem may be the encoding in /etc/sysconfig/i18n file. If
1027  the language encoding is </p>  the language encoding is </p>
1028      <pre>       LANG="en_US.UTF-8"<br>          </pre>      <pre>       LANG="en_US.UTF-8"<br />                </pre>
1029  changing it to  changing it to
1030      <pre>       LANG="en_US"<br>                </pre>      <pre>       LANG="en_US"<br />              </pre>
1031  should fix the problem.  should fix the problem.
1032      <p></p>      <p></p>
1033    </li>    </li>
# Line 1094  Line 1096 
1096        <li>Create a file named ".options" in you eclipse directory (the        <li>Create a file named ".options" in you eclipse directory (the
1097  directory that contains the executable) that contains the following 2  directory that contains the executable) that contains the following 2
1098  lines that enable CVS debugging.  lines that enable CVS debugging.
1099          <pre>           org.eclipse.team.cvs.core/debug=true<br>                org.eclipse.team.cvs.core/cvsprotocol=true<br>          </pre>          <pre>           org.eclipse.team.cvs.core/debug=true<br />              org.eclipse.team.cvs.core/cvsprotocol=true<br />                </pre>
1100        </li>        </li>
1101        <li>Start Eclipse with the following parameters tailored to you        <li>Start Eclipse with the following parameters tailored to you
1102  local setup (The below example is for windows). The important aspects  local setup (The below example is for windows). The important aspects
1103  are the use of java.exe instead of javaw.exe and the inclusion of the  are the use of java.exe instead of javaw.exe and the inclusion of the
1104  -debug and -consolelog options. These will cause the debug console to  -debug and -consolelog options. These will cause the debug console to
1105  be visible and for debugging output to appear in the console.  be visible and for debugging output to appear in the console.
1106          <pre>           C:\eclipse\eclipse.exe<br>                 -vm C:\jre\bin\java.exe<br>             -data C:\eclipse\workspace<br>                  -debug<br>              -consolelog<br>              </pre>          <pre>           C:\eclipse\eclipse.exe<br />               -vm C:\jre\bin\java.exe<br />                   -data C:\eclipse\workspace<br />                -debug<br />            -consolelog<br />            </pre>
1107        </li>        </li>
1108        <li>Inside Eclipse, create your repo location and expand it in        <li>Inside Eclipse, create your repo location and expand it in
1109  the repositories view (for example). The CVS command traffic in the  the repositories view (for example). The CVS command traffic in the
1110  debug console should contains an invocation of the update command that  debug console should contains an invocation of the update command that
1111  looks something like (this is output from dev.eclipse.org):  looks something like (this is output from dev.eclipse.org):
1112          <pre>           CMD&gt; cvs -n update -d "."<br>                ...<br>         update<br>              E cvs server: Updating .<br>            E cvs server: New directory `CVSROOT' -- ignored<br>            E cvs server: New directory `jdt-core-home' -- ignored<br>              E cvs server: New directory `jdt-debug-home' -- ignored<br>             ...<br>         </pre>          <pre>           CMD&gt; cvs -n update -d "."<br />              ...<br />               update<br />            E cvs server: Updating .<br />          E cvs server: New directory `CVSROOT' -- ignored<br />          E cvs server: New directory `jdt-core-home' -- ignored<br />            E cvs server: New directory `jdt-debug-home' -- ignored<br />           ...<br />               </pre>
1113        </li>        </li>
1114      </ol>      </ol>
1115    </li>    </li>
# Line 1176  Line 1178 
1178      <p>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; </p>      <p>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; </p>
1179      <p>Eclipse 2.1 supports CVS Edit/Unedit. In 2.0, you can use the      <p>Eclipse 2.1 supports CVS Edit/Unedit. In 2.0, you can use the
1180  following workaround:</p>  following workaround:</p>
1181      <pre>               Run-&gt;External Tools-&gt;Configure...-&gt;New<br>             Name: CVS Watchers<br>          Tool Location: C:\cygwin\bin\cvs.exe<br>                Tool arguments: watchers<br>            Working directory: ${container_loc}<br>         After running, refresh: Nothing<br>             Check Show Execution Log on Console<br>         OK<br>          New<br>         Name: CVS Edit<br>              Tool Location: C:\cygwin\bin\cvs.exe<br>                Tool arguments: edit ${resource_name}<br>               Working directory: ${container_loc}<br>         After running, refresh: Nothing<br>             Check Show Execution Log on Console<br>         OK<br>          </pre>      <pre>               Run-&gt;External Tools-&gt;Configure...-&gt;New<br />           Name: CVS Watchers<br />                Tool Location: C:\cygwin\bin\cvs.exe<br />              Tool arguments: watchers<br />          Working directory: ${container_loc}<br />               After running, refresh: Nothing<br />           Check Show Execution Log on Console<br />               OK<br />                New<br />               Name: CVS Edit<br />            Tool Location: C:\cygwin\bin\cvs.exe<br />              Tool arguments: edit ${resource_name}<br />             Working directory: ${container_loc}<br />               After running, refresh: Nothing<br />           Check Show Execution Log on Console<br />               OK<br />                </pre>
1182      <p> Unedit works the same as Edit, Editors works the same way as      <p> Unedit works the same as Edit, Editors works the same way as
1183  Watchers. To use the tools, highlight the file or directory on which to  Watchers. To use the tools, highlight the file or directory on which to
1184  execute the CVS command, then select Run-&gt;External Tools-&gt;<tool  execute the CVS command, then select Run-&gt;External Tools-&gt;<tool

Legend:
Removed from v.1.53  
changed lines
  Added in v.1.54