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

Parent Directory Parent Directory | Revision Log Revision Log


Revision 1.51 - (view) (download) (as text)

1 : jlemieux 1.44 <!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd">
2 : jlemieux 1.48 <html xmlns="http://www.w3.org/1999/xhtml" xml:lang="en">
3 : jlemieux 1.44 <head>
4 : jlemieux 1.48 <meta content="application/xhtml+xml; charset=utf-8"
5 :     http-equiv="content-type">
6 :     <meta content="haran" name="author">
7 :     <meta content="Windows Notepad" name="generator">
8 :     <link type="text/css" href="http://dev.eclipse.org/default_style.css"
9 :     rel="stylesheet">
10 :     <link title="Grey boxes stylesheet"
11 : jlemieux 1.44 href="http://dev.eclipse.org/viewcvs/index.cgi/%7Echeckout%7E/platform-vcm-home/layout.css"
12 : jlemieux 1.48 type="text/css" rel="stylesheet">
13 :     <link
14 :     href="http://dev.eclipse.org/viewcvs/index.cgi/%7Echeckout%7E/platform-vcm-home/colors.css"
15 :     type="text/css" rel="stylesheet">
16 : mvalenta 1.49 <title>Eclipse Platform - CVS FAQ</title>
17 : jlemieux 1.44 </head>
18 :     <body>
19 : jlemieux 1.48 <table width="100%" cellpadding="2" cellspacing="5" border="0">
20 : jlemieux 1.44 <tbody>
21 :     <tr>
22 : jlemieux 1.48 <td width="72%" align="left"> <font class="indextop"> CVS</font><br>
23 : jlemieux 1.44 <font class="indexsub">platform cvs support</font></td>
24 : jlemieux 1.48 <td width="28%"><img width="120" height="86"
25 :     src="http://dev.eclipse.org/images/Idea.jpg"></td>
26 : jlemieux 1.44 </tr>
27 :     </tbody>
28 :     </table>
29 : jlemieux 1.41 <h1>CVS Eclipse Plug-in FAQ</h1>
30 : mvalenta 1.51 <p>Last Modified: $Date: 2005/04/04 17:49:12 $</p>
31 : james 1.1 <ul>
32 : jlemieux 1.44 <li><b><a href="#gettingStarted">Getting started</a></b>
33 : jlemieux 1.36 <ol>
34 : jlemieux 1.44 <li><a href="#gettingStarted_1">How do I get a project into my
35 :     workspace from CVS?</a></li>
36 :     <li><a href="#gettingStarted_2">How do I put a project into CVS
37 :     from my workspace?</a></li>
38 :     <li><a href="#gettingStarted_3">I already have a project checked
39 :     out from CVS with the command-line tool. How do I use it in Eclipse
40 :     without having to check out the whole project again?</a></li>
41 : jlemieux 1.36 </ol>
42 :     </li>
43 : jlemieux 1.44 <li><b><a href="#browsing">Browsing the Repository</a></b>
44 : jlemieux 1.36 <ol>
45 : jlemieux 1.44 <li><a href="#browsing_1">Why don't my branches and versions show
46 :     up when I am browsing?</a></li>
47 :     <li><a href="#browsing_2">Why do some modules defined in
48 :     CVSROOT/modules appear empty in the CVS Repositories view?</a></li>
49 :     <li><a href="#browsing_3">When I expand HEAD in the CVS
50 :     Repositories View, it is always empty even though I know the repository
51 :     has contents. Whats wrong?</a></li>
52 : jlemieux 1.36 </ol>
53 :     </li>
54 : jlemieux 1.44 <li><b><a href="#server">Server Issues</a></b>
55 : kevinm 1.15 <ol>
56 : jlemieux 1.44 <li><a href="#server_1">What server versions of CVS are supported
57 :     by Eclipse?</a></li>
58 :     <li><a href="#server_1a">Why doesn't Eclipse 2.1.x work with CVS
59 :     server versions 1.11.7 and beyond?</a></li>
60 : kevinm 1.15 <li><a href="#server_cvsnt">Why isn't CVSNT supported?</a></li>
61 :     <li><a href="#server_2">Where can I get CVS for UNIX or Windows?</a></li>
62 :     <li><a href="#server_3">Where can I find documentation on CVS?</a></li>
63 : jlemieux 1.44 <li><a href="#server_4">I'm having problems running CVSNT
64 :     1.11.1.1 on Windows 2000, what's wrong?</a></li>
65 :     <li><a href="#server_5">I use logical repository mapping under
66 :     CVSNT 1.11.1.3, but Eclipse complains. What's wrong?</a></li>
67 :     <li><a href="#server_6">When I perform a Replace With or Update
68 :     operation, Eclipse tells me that option -C is not supported. What's
69 :     wrong?</a></li>
70 :     <li><a href="#server_7">I performed a Replace With or Override
71 :     and Update and one of the files involved ended up with strange
72 :     characters in it. Why?</a></li>
73 :     <li><a href="#server_8">I got a "received broken pipe signal"
74 :     error. What does it mean?</a></li>
75 :     <li><a href="#server_9">How do I use a local connection with
76 :     Eclipse?</a></li>
77 :     <li><a href="#server_10">When using CVSNT, why do I get the error
78 :     "Error fetching file revisions" when synchronizing?</a></li>
79 :     <li><a href="#server_11">Why can't I get Eclipse to work with
80 :     CVSNT and mapped network drives?</a></li>
81 :     <li><a href="#server_12">Using CVSNT, Why do I get the error "cvs
82 :     [server aborted]: cannot find .: No such file or directory"?</a></li>
83 :     <li><a href="#server_13">My server has been configured to use an
84 :     alternate server name. What do I need to do?</a></li>
85 : jlemieux 1.36 </ol>
86 :     </li>
87 : jlemieux 1.44 <li><b><a href="#ssh">Using SSH with CVS</a></b>
88 : jlemieux 1.36 <ol>
89 : jlemieux 1.44 <li><a href="#ssh_1">How do I use SSH to communicate with the
90 :     server?</a></li>
91 :     <li><a href="#ssh_2">What is the difference between ext and
92 :     extssh?</a></li>
93 : jlemieux 1.36 <li><a href="#ssh_jcraft">My SSH server only support SSH2 protocol</a></li>
94 :     <li><a href="#ssh_3">How do I set up public-key authentication?</a></li>
95 : jlemieux 1.44 <li><a href="#ssh_4">When I try to connect using SSH, it tells me
96 :     "Could not chdir to home directory /home/user/myname". What did I do
97 :     wrong?</a></li>
98 :     <li><a href="#ssh_5">I got an 'Unknown response' while trying to
99 :     perform CVS browsing. What went wrong?</a></li>
100 :     </ol>
101 :     </li>
102 :     <li><b><a href="#10">Upgrading from Eclipse 1.0</a></b>
103 :     <ol>
104 :     <li><a href="#10_1">Is there anything I should do before
105 :     upgrading from Eclipse 1.0 to 2.0?</a></li>
106 :     <li><a href="#10_2">I'm using a workspace from 1.0. Why does the
107 :     Team menu only contain "Share Project"?</a></li>
108 :     <li><a href="#10_3">Eclipse 1.0 created all my files as binary in
109 :     the repository. How do I fix this?</a></li>
110 :     <li><a href="#10_4">Is a Branch the same as a Stream? What about
111 :     other 1.0 terminology?</a></li>
112 :     <li><a href="#10_5">I get a message saying the .vcm_meta file is
113 :     obsolete and should be deleted. Should I really delete it?</a></li>
114 :     </ol>
115 :     </li>
116 :     <li><b><a href="#java">Using Eclipse and CVS for Java development</a></b>
117 :     <ol>
118 :     <li><a href="#java_1">When I check out a Java project from the
119 :     repository, how do I make Eclipse aware it is a Java project?</a></li>
120 :     <li><a href="#java_2">What is the .classpath file? Should I
121 :     release it to the repository?</a></li>
122 :     <li><a href="#java_3">In my CVS repository, there is a source
123 :     directory in the repository root. How can I use this with Eclipse?</a></li>
124 :     <li><a href="#java_4">How do I check out a module definition as a
125 :     Java project</a></li>
126 :     <li><a href="#java_5">Why does the bin directory keep appearing
127 :     in the Synchronize view?</a></li>
128 :     <li><a href="#java_5a">I ignored the bin directory but it appears
129 :     to be shared anyway. Why?</a></li>
130 : jlemieux 1.36 <li><a href="#java_6">How do I use CVS keywords in Java templates?</a></li>
131 : jlemieux 1.44 <li><a href="#java_7">I'm working with a virtual module defined
132 :     in the CVSROOT/modules file. How do I commit the .project and/or
133 :     .classpath file?</a></li>
134 : jlemieux 1.36 </ol>
135 :     </li>
136 : jlemieux 1.44 <li><b><a href="#commandLine">Compatibility Between CVS command-line
137 :     client and Eclipse</a></b>
138 : jlemieux 1.36 <ol>
139 : jlemieux 1.44 <li><a href="#commandLine_1">Does Eclipse use [WinCVS|CVS
140 :     command-line client] to talk to the server?</a></li>
141 :     <li><a href="#commandLine_2">The command-line CVS client stores
142 :     information in CVS folders. Does Eclipse do the same thing? If so,
143 :     where are the folders?</a></li>
144 :     <li><a href="#commandLine_3">Is Eclipse compatible with the
145 :     command-line CVS client?</a></li>
146 :     <li><a href="#commandLine_4">Can I import a project into Eclipse
147 :     that was checked out using the command line?</a></li>
148 :     <li><a href="#commandLine_5">Why does Eclipse corrupt my *.jar,
149 :     *.zip, etc. files?</a></li>
150 :     <li><a href="#commandLine_6">When I use the command-line CVS on
151 :     my project, why do the CVS folders sometimes appear in the Navigator
152 :     View?</a></li>
153 :     <li><a href="#commandLine_7">When I use the command-line CVS on
154 :     my project, why go I get "resource out of sync" errors?</a></li>
155 : jlemieux 1.36 </ol>
156 :     </li>
157 : jlemieux 1.44 <li><b><a href="#patches">Working with Patches</a></b>
158 : jlemieux 1.36 <ol>
159 :     <li><a href="#patches_1">How do I send someone a patch?</a></li>
160 : jlemieux 1.44 <li><a href="#patches_2">How do I apply a patch that someone sent
161 :     me?</a></li>
162 : jlemieux 1.36 </ol>
163 :     </li>
164 : jlemieux 1.44 <li><b><a href="#linux">Linux Issues</a></b>
165 : jlemieux 1.36 <ol>
166 : jlemieux 1.44 <li><a href="#linux_0">On linux, using IBM JRE 1.3.0, I get a
167 :     timeout when connecting to a repository. What's wrong?</a></li>
168 :     <li><a href="#linux_1">On Red Hat 8, Eclipse fails to make a
169 :     checkout but it works with other clients. Why?</a></li>
170 : jlemieux 1.36 </ol>
171 :     </li>
172 : jlemieux 1.44 <li><b><a href="#windows">Windows Issues</a></b>
173 : jlemieux 1.36 <ol>
174 : jlemieux 1.44 <li><a href="#windows_0">Eclipse crashed Windows 2000 (blue
175 :     screen) when performing a CVS operation. What happened?</a></li>
176 :     <li><a href="#windows_2">Eclipse always times out when performing
177 :     a Synchronize on one or two particular machines?</a></li>
178 :     <li><a href="#windows_3">Why do CVS operations slow down when I
179 :     am connected to my network/dial-up?</a></li>
180 :     <li><a href="#windows_4">Why do all my files show as outgoing
181 :     changes?</a></li>
182 : jlemieux 1.36 </ol>
183 :     </li>
184 : jlemieux 1.44 <li><b><a href="#misc">Miscellaneous</a></b>
185 : jlemieux 1.36 <ol>
186 : jlemieux 1.44 <li><a href="#misc_0">Is there any equivalent to CVS_CLIENT_LOG
187 :     is Eclipse?</a></li>
188 :     <li><a href="#misc_1">What is the .project file, and should I
189 :     release it to CVS?</a></li>
190 :     <li><a href="#misc_2">I don't have update access to the CVS
191 :     repository. Can I still check out a project with Eclipse?</a></li>
192 :     <li><a href="#misc_3">What does "Terminated with fatal signal 10"
193 :     mean?</a></li>
194 :     <li><a href="#misc_4">I copied some folders from one CVS project
195 :     to another and the old CVS information remained. What happened?</a></li>
196 :     <li><a href="#misc_8">I used Team &gt; Share Project to connect a
197 :     local project to an existing project and it takes forwever. Why?</a></li>
198 : jlemieux 1.36 <li><a href="#misc_9">Does Eclipse support Watch/Edit?</a></li>
199 : jlemieux 1.44 <li><a href="#misc_12">Why do I get a "Pre-commit failed" error
200 :     with no detailed error message?</a></li>
201 : kevinm 1.15 </ol>
202 : jlemieux 1.36 </li>
203 : james 1.1 </ul>
204 :     <!-- End of table of contents -->
205 :     <!-- Getting Started -->
206 : jlemieux 1.42 <h1>Getting Started</h1>
207 : james 1.1 <ol>
208 : jlemieux 1.44 <li><b><a name="gettingStarted_1">How do I get a project into my
209 :     workspace from CVS?</a></b>
210 :     <p>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; </p>
211 :     <ol>
212 :     <li>Window-&gt;Show View-&gt;Other. Select CVS-&gt;CVS
213 :     Repositories.</li>
214 :     <li>Context Menu-&gt;New-&gt;Repository Location...</li>
215 :     <li>Fill in the location information identifying your repository
216 :     and click Finish.</li>
217 :     <li>Expand the newly-created repository location.</li>
218 :     <li>Expand HEAD.</li>
219 :     <li>Find the module you are interested in.</li>
220 :     <li>Context Menu-&gt;Check Out As Project.</li>
221 :     </ol>
222 :     <br>
223 :     The project now exists in your workspace. </li>
224 :     <p>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; <br>
225 :     </p>
226 :     <li><b><a name="gettingStarted_2">How do I put a project into CVS
227 :     from my workspace?</a></b>
228 :     <p>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; </p>
229 :     <ol>
230 :     <li>Select the project in the Navigator or other view.</li>
231 :     <li>Context Menu-&gt;Team-&gt;Share Project...</li>
232 :     <li>Fill in the location information identifying your repository
233 :     and click Finish.</li>
234 :     <li>The Synchronize view opens, showing all your outgoing changes.</li>
235 :     <li>Select the project in the Synchronize view.</li>
236 :     <li>Context Menu-&gt;Commit.</li>
237 :     <li>Answer yes when prompted to add new files to version control.</li>
238 :     <li>Supply a release comment if you like.</li>
239 :     </ol>
240 :     <br>
241 :     The project now exists in the repository. </li>
242 :     <p>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; <br>
243 :     </p>
244 :     <li><b><a name="gettingStarted_3">I already have a project checked
245 :     out from CVS with the command-line tool. How do I use it in Eclipse
246 :     without having to check out the whole project again?</a></b>
247 :     <p>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; </p>
248 :     <ol>
249 :     <li>Create a project in the workspace.</li>
250 :     <li>File-&gt;Import, select File System, locate your files, click
251 :     Finish.</li>
252 :     <li>Select the project in the Navigator or other view.</li>
253 :     <li>Context Menu-&gt;Team-&gt;Share Project...</li>
254 :     <li>The wizard should tell you that it found all the necessary
255 :     information. Click Finish.</li>
256 :     </ol>
257 :     <br>
258 :     Eclipse has now shared the project with the CVS repository. </li>
259 :     <p>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; </p>
260 : james 1.1 </ol>
261 :     <br>
262 :     <!-- Browsing the Repository -->
263 : jlemieux 1.42 <h1>Browsing the Repository</h1>
264 : james 1.1 <ol>
265 : jlemieux 1.44 <li><b><a name="browsing_1">Why don't my branches and versions show
266 :     up when I am browsing?</a></b>
267 :     <p>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; </p>
268 :     <p>When you are browsing in the CVS Repositories view, you may
269 :     expect to see branch and version tags which you have previously
270 :     created. In CVS, such tags are stored on individual files rather than
271 :     on projects or folders. Rather than scan every file in the repository,
272 :     Eclipse only scans one well-known file, .project, which should exist in
273 :     every Eclipse project. It is possible that you have other interesting
274 :     tags that do not appear on .project but which you would like to show up
275 :     in the CVS Repositories view.</p>
276 :     <p>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; </p>
277 :     <p>To make these tags appear, do the following:</p>
278 :     <ol>
279 :     <li>Open the CVS Repositories view.</li>
280 :     <li>Expand HEAD and select the project for which you want to
281 :     configure tags.</li>
282 :     <li>Context Menu-&gt;Configure Branches and Versions...</li>
283 :     <li>In the "Browse files for tags" table, select one or more
284 :     files that contain tags you would like to see.</li>
285 :     <li>Click "Add Selected Tags".</li>
286 :     <li>Click "OK".</li>
287 :     </ol>
288 :     <br>
289 :     The CVS Repositories view will now display the chosen tags under the
290 :     Branches and Versions categories. In addition, these tags will show up
291 :     in other tag-related operations, such as "Replace With-&gt;Branch or
292 :     Version...". </li>
293 :     <p>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; </p>
294 :     <li><b><a name="browsing_2">Why do some modules defined in
295 :     CVSROOT/modules appear empty in the CVS Repositories view?</a></b>
296 :     <p>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; </p>
297 :     <p>Some modules are not expandable because their definition is
298 :     complex and difficult to parse on the client. These modules can still
299 :     be checked out properly using the "Check Out Module" menu command from
300 :     the module's context menu. </p>
301 :     </li>
302 :     <p>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; </p>
303 :     <li><b><a name="browsing_3">When I expand HEAD in the CVS
304 :     Repositories View, it is always empty even though I know the repository
305 :     has contents. Whats wrong?</a></b>
306 :     <p>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; </p>
307 :     <p>If you also see messages from the server like "-f server: ...",
308 :     this indicates that your CVS server has not been configured properly.
309 :     Here is the line as it should appear in the "/etc/inetd.conf" file
310 :     (example from AIX but the problem has also been seen on Solaris):</p>
311 :     <ul>
312 :     <li>cvspserver stream tcp nowait root /usr/bin/cvs cvs -f
313 :     --allow-root=/usr/cvsroot pserver</li>
314 :     </ul>
315 :     <p>The key is the 2nd copy of "cvs". The online cvs book at <a
316 :     href="http://cvsbook.red-bean.com/cvsbook.html#The_pserver_access_method_is_not_working">
317 : mvalenta 1.28 http://cvsbook.red-bean.com/cvsbook.html</a>
318 : jlemieux 1.44 has it right (although I thought it was a typo so never tried it). Look
319 :     for "The pserver access method is not working" section. Part of the
320 :     reason I got this wrong is that the linux xinetd configuration
321 :     does not duplicate the name of the program. At one point I
322 : mvalenta 1.28 just copied the fields from the linux config into the fields in the AIX
323 : jlemieux 1.44 inetd.conf file. Now that I know what to look for, the other entries in
324 :     the inetd.conf file
325 : mvalenta 1.28 have the program name duplicated.</p>
326 : jlemieux 1.44 </li>
327 :     <p>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; </p>
328 : james 1.1 </ol>
329 :     <br>
330 : kevinm 1.16 <!-- Server Issues -->
331 : jlemieux 1.43 <h1>Server Issues</h1>
332 : james 1.1 <ol>
333 : jlemieux 1.48 <li><b><a name="server_1">What server versions of CVS are supported
334 :     by Eclipse?</a></b>
335 : jlemieux 1.44 <p>&nbsp; </p>
336 : jlemieux 1.48 <p>In 3.0, Eclipse supports CVS version 1.11.1p1 or higher, running
337 : mvalenta 1.49 on a Linux or UNIX server and CVSNT 2.0.58d or later, when properly
338 :     <a href="../html-cvs/cvs-compatibility.html">configured</a>. Eclipse 2.1.2 and before does not work with
339 : jlemieux 1.48 CVS versions greater than 1.11.6 (see <a href="#server_1a">next point</a>).
340 : mvalenta 1.49 CVSNT versions prior to 2.0.58d are not supported but some versions have been reported to
341 :     work with few problems.
342 :     There have also been some
343 : jlemieux 1.48 problems reported with HPUX and Solaris version (see <a
344 : jlemieux 1.44 href="#browsing_3">above</a>). </p>
345 :     </li>
346 : jlemieux 1.48 <li><b><a name="server_1a">Why doesn't Eclipse 2.1.x work with CVS
347 :     server versions 1.11.7 and beyond?</a></b>
348 : jlemieux 1.44 <p>&nbsp; </p>
349 : jlemieux 1.48 <p>Most of the interesting Eclipse CVS functionality relies on the
350 :     format of the messages and the change in format made in 1.11.7 breaks
351 :     the parsing in Eclipse versions proir to 2.1.3. Most of the
352 :     incompatibilities for 1.11.x were adressed in 2.1.3. See bugs <a
353 :     href="https://bugs.eclipse.org/bugs/show_bug.cgi?id=46655">46655</a>
354 :     and <a href="https://bugs.eclipse.org/bugs/show_bug.cgi?id=49056">49056</a>
355 :     for patches and workarounds for previous versions of Eclipse or
356 :     remaining incompatibilities. As for 1.12.x releases of CVS, Eclipse
357 :     2.1.x is not compatible with this server version. Eclipse 3.0 is
358 :     compatible with 1.12.7 but future releases of CVS may cause similar
359 :     breakages. In such cases, Team&gt;Update and Team&gt;Commit should
360 :     still work but the more advanced workflows (e.g. synchronizing) may not
361 :     be reliable.</p>
362 :     </li>
363 : mvalenta 1.49 <li><b><a name="server_cvsnt">Why aren't older (pre 2.0.58d) CVSNT versions supported?</a></b>
364 :     <p>The reason older CVSNT versions aren't supported is because traditionally its
365 :     development effort had been smaller and has lagged behind that of CVS
366 :     Linux, thus its quality tends to be of issue. That has changed as of version 2.0.58d
367 :     which is now supported (when properly
368 :     <a href="../html-cvs/cvs-compatibility.html">configured</a>) on Eclipse 3.0 and beyond.</p>
369 : mvalenta 1.47 </li>
370 : jlemieux 1.48 <li><b><a name="server_2">Where can I get CVS for UNIX or Windows?</a></b>
371 : jlemieux 1.44 <p>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; </p>
372 :     <p>CVS for UNIX can be downloaded from <a
373 : jlemieux 1.48 href="http://www.cvshome.org">http://www.cvshome.org</a>. CVSNT can be
374 :     downloaded from <a href="http://www.cvsnt.org">http://www.cvsnt.org</a>.</p>
375 : jlemieux 1.44 </li>
376 :     <p>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; </p>
377 : jlemieux 1.48 <li><b><a name="server_3">Where can I find documentation on CVS?</a></b>
378 : jlemieux 1.44 <p>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; </p>
379 :     <p>The CVS manual can be browsed online at <a
380 : jlemieux 1.48 href="http://www.cvshome.org/docs/manual/">http://www.cvshome.org/docs/manual/</a>.
381 :     The CVS FAQ-O-Matic can be found at <a
382 : jlemieux 1.44 href="http://ccvs.cvshome.org/fom/fom.cgi">http://ccvs.cvshome.org/fom/fom.cgi</a>.</p>
383 :     </li>
384 :     <p>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; </p>
385 : jlemieux 1.48 <li><b><a name="server_4">I'm having problems running CVSNT 1.11.1.1
386 :     on Windows 2000, what's wrong?</a></b>
387 : jlemieux 1.44 <p>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; </p>
388 : jlemieux 1.48 <p>We have reports that CVSNT 1.11.1.1 (and perhaps later versions)
389 :     will not run on Windows 2000 unless Service Pack 2 or later is
390 :     installed.</p>
391 : jlemieux 1.44 </li>
392 :     <p>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; </p>
393 : jlemieux 1.48 <li><b><a name="server_5">I use logical repository mapping under
394 :     CVSNT 1.11.1.3, but Eclipse complains. What's wrong?</a></b>
395 : jlemieux 1.44 <p>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; </p>
396 : jlemieux 1.48 <p>You have set up relative mapping (repository prefix) under
397 :     CVSNT, so that, for example, "D:\cvs\repo" maps to "/REPO". That means
398 :     you should be able to use ":pserver:user@host:/REPO". However, CVSNT
399 :     does not always communicate these paths to the client properly; in
400 :     particular, Eclipse needs information for synchronization which is not
401 :     included in this mode of operation. The solution is to change your
402 :     CVSNT server settings to disable the use of a repository prefix, and
403 :     use the full path of the repository, thus:
404 :     ":pserver:user@host:D:\cvs\repo".</p>
405 : jlemieux 1.44 </li>
406 :     <p>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; </p>
407 : jlemieux 1.48 <li><b><a name="server_6">When I perform a Replace With or Update
408 :     operation, Eclipse tells me that option -C is not supported. What's
409 :     wrong?</a></b>
410 : jlemieux 1.44 <p>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; </p>
411 : jlemieux 1.48 <p>This error indicates that your server version is CVS 1.10 or
412 :     before. The -C option was introduced in version 1.11. See <a
413 : jlemieux 1.44 href="#server_1">above</a> for supported CVS versions.</p>
414 :     </li>
415 :     <p>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; </p>
416 : jlemieux 1.48 <li><b><a name="server_7">I performed a Replace With or Override and
417 :     Update and one of the files involved ended up with strange characters
418 :     in it. Why?</a></b>
419 : jlemieux 1.44 <p>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; </p>
420 : jlemieux 1.48 <p>This error indicates that your server version is CVS 1.11 which
421 :     has a bug when replacing a locally dirty file. See <a href="#server_1">above</a>
422 :     for supported CVS versions.</p>
423 : jlemieux 1.44 </li>
424 :     <p>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; </p>
425 : jlemieux 1.48 <li><b><a name="server_8">I got a "received broken pipe signal"
426 :     error. What does it mean?</a></b>
427 : jlemieux 1.44 <p>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; </p>
428 : jlemieux 1.48 <p>Eclipse sometime performs multiple commands within a single
429 :     connection to the server. This may cause problems with CVS server that
430 :     are running server scripts in reponse to certain commands.</p>
431 : jlemieux 1.44 </li>
432 :     <p>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; </p>
433 : jlemieux 1.48 <li><b><a name="server_9">How do I use a local connection with
434 :     Eclipse?</a></b>
435 : jlemieux 1.44 <p>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; </p>
436 : jlemieux 1.48 <p>Eclipse does not support the use of the local connection method
437 :     as this requires a CVS client that also includes the CVS server code in
438 :     it. Command line cvs uses the same executable for the client and the
439 :     server whereas Eclipse is a client only. Since the repository is on the
440 :     same machine as the client, you should be able to use pserver.</p>
441 : jlemieux 1.44 </li>
442 :     <p>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; </p>
443 : jlemieux 1.48 <li><b><a name="server_10">When using CVSNT, why do I get the error
444 :     "Error fetching file revisions" when synchronizing?</a></b>
445 : jlemieux 1.44 <p>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; </p>
446 : jlemieux 1.48 <p>This error, or an error stating that "An error has occurred
447 :     processing file &lt;repo file&gt; &lt;revision&gt;", occur when the
448 :     CVSNT server has been configured to use a repository prefix (also
449 :     referred to as a repository alias). CVSNT provides this mechanism to
450 :     allow compatibility with the Unix/Linux based command line tools.
451 :     However, the CVSNT server does not properly map the repository paths
452 :     that are communicated in text messages. The Eclipse CVS client relies
453 :     on these text messages to provide advanced features such as
454 :     synchronization and compare. In order for these features to work
455 :     properly, the CVSNT server must not be configured to use a repository
456 :     prefix. Instead, the full path name (i.e. D:\cvs\root) must be used
457 :     (see related question <a href="#server_5">above</a>). </p>
458 : jlemieux 1.44 </li>
459 :     <p>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; </p>
460 : jlemieux 1.48 <li><b><a name="server_11">Why can't I get Eclipse to work with CVSNT
461 :     and mapped network drives?</a></b>
462 : jlemieux 1.44 <p>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; </p>
463 : jlemieux 1.48 <p>The problem is that CVSNT (as of 1.11.1.3) only supports using
464 :     the local connection method with network drives and Eclipse does not
465 :     support this connection method (see <a href="#server_9">above</a>). </p>
466 : jlemieux 1.44 </li>
467 :     <p>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; </p>
468 : jlemieux 1.48 <li><b><a name="server_12">Using CVSNT, Why do I get the error "cvs
469 :     [server aborted]: cannot find .: No such file or directory"?</a></b>
470 : jlemieux 1.44 <p>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; </p>
471 : jlemieux 1.48 <p>I think the problem is that of user rights on the machine CVSNT
472 :     is running on. You might try one or more of the following options: </p>
473 : mvalenta 1.33 <ul>
474 : jlemieux 1.48 <li>create a group having full access rights to the CVSNT
475 :     repository directory structure plus the temp folder CVSNT is using.
476 :     This is easiest if you specify a separate CVSNT temp directory such as
477 :     "c:\cvstemp" using the Advanced tab in the<br>
478 :     CVSNT control panel.&nbsp; (The default temporary directories in
479 :     "C:\WINNT\TEMP" and "C:\Documents and Settings" have access
480 :     restrictions under Win2000 and WinXP).</li>
481 : jlemieux 1.44 <li>turn off impersonation in CVSNT</li>
482 : jlemieux 1.48 <li>add all CVS users to PowerUsers on the machine CVSNT is
483 :     running on</li>
484 : jlemieux 1.44 </ul>
485 :     <p></p>
486 : mvalenta 1.40 <p></p>
487 : mvalenta 1.33 </li>
488 : jlemieux 1.48 <li><b><a name="server_13">My server has been configured to use an
489 :     alternate server name. What do I need to do?</a></b>
490 : jlemieux 1.44 <p>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; </p>
491 : jlemieux 1.48 <p>Custom server names cause problems for Eclipse CVS because the
492 :     client makes use of the text messages sent from the server. The symptom
493 :     you will see is that expanding HEAD will not show any of the folders in
494 :     the repository. To correct the problem: </p>
495 : jlemieux 1.44 <ol>
496 :     <li>Open the CVS Repositories View. </li>
497 : jlemieux 1.48 <li>From the context menu of the repository location, open the
498 :     Properties page. </li>
499 :     <li>On the CVS properties page (the only one present), select
500 :     "Expect a custom program name" (at the bottom) and enter "cvspserver". </li>
501 : jlemieux 1.44 </ol>
502 : jlemieux 1.48 This should fix the problem. </li>
503 : jlemieux 1.44 <p>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; </p>
504 : james 1.1 </ol>
505 :     <br>
506 :     <!-- SSH -->
507 : jlemieux 1.43 <h1>Using SSH with CVS</h1>
508 : james 1.1 <ol>
509 : jlemieux 1.44 <li><b><a name="ssh_1">How do I use SSH to communicate with the
510 :     server?</a></b>
511 :     <p>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; </p>
512 :     <p>The pserver protocol sends passwords over the network in
513 :     plaintext. Many people prefer to establish a secure connection using
514 :     SSH. Eclipse supports two methods of connecting to CVS repositories
515 :     using SSH. </p>
516 :     <p>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; </p>
517 :     <p>To use the Eclipse's built-in SSH support, simply specify
518 :     "extssh" as the connection method type when creating the repository
519 :     connection.</p>
520 :     <p>To use SSH support from an external tool, you must: </p>
521 :     <ol>
522 :     <li>Specify "ext" as the connection method type when creating the
523 :     repository connection.</li>
524 :     <li>Window-&gt;Preferences-&gt;Team-&gt;CVS-&gt;Ext Connection
525 :     Method. On this page, specify the name and location of your external
526 :     ssh client. (For example, "<code>C:\plink.exe</code>" or "<code>/usr/local/bin/ssh</code>").
527 :     Also specify the name and location of the CVS binary <b>on the server</b>.
528 :     The default value is often correct.</li>
529 :     <li>Ensure that you can log on to the server using the external
530 :     SSH tool <b>without specifying a password</b>.</li>
531 :     </ol>
532 :     <p><b>Note:</b> In Eclipse 2.1, you can also specify (on the Ext
533 :     Connection Method preference page) the parameters to be passed to the
534 :     SSH client, including the password.</p>
535 :     </li>
536 :     <p>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; </p>
537 :     <li><b><a name="ssh_2">What is the difference between ext and extssh?</a></b>
538 :     <p>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;The extssh connection method uses
539 :     a built-in SSH client. The ext connection method allows you to specify
540 :     an external SSH client to use. For extssh to work, the server must be
541 :     running an SSH server with SSH1 protocol compatibility. If extssh does
542 :     not work, it is likely that the server is running only the SSH2
543 :     protocol. If this is the case, you must configure the ext connection
544 :     method with an external SSH client. <br>
545 :     <br>
546 :     </p>
547 :     </li>
548 :     <li><a name="ssh_jcraft"></a><strong>My SSH server only support SSH2
549 :     protocol</strong><br>
550 : jlemieux 1.36 <br>
551 : jlemieux 1.44 Eclipse comes with a built-in SSH connection method called 'extssh'.
552 :     However this method only supports SSH1 servers. If your server is
553 :     running SSH2 and you want to use Eclipse to connect to that server you
554 :     have two options: <br>
555 : jlemieux 1.36 <br>
556 :     <ol>
557 : jlemieux 1.44 <li>use a command line SSH client that supports SSH2 with the
558 :     'ext' connection method <br>
559 :     </li>
560 :     <li>download a plugin created by <a
561 :     href="http://www.jcraft.com/eclipse-cvsssh2/">JCraft</a> that provides
562 :     a SSH2 connection method. <br>
563 : jlemieux 1.36 <br>
564 : jlemieux 1.44 </li>
565 : jlemieux 1.36 </ol>
566 : jlemieux 1.44 To use the 'ext' connection method, download and install an SSH command
567 :     line client for your operating environment. In the Team &gt; CVS &gt;
568 :     Ext Connection Method preference page, configure the location of the
569 :     SSH executable and how the executable is to be called. For the ext
570 :     method to work the CVS client on your server must support the server
571 :     mode. You can verify this by running cvs --help-commands and ensure
572 :     that the server command is supported.<br>
573 :     &nbsp; </li>
574 :     <li><b><a name="ssh_3">How do I set up public-key authentication?</a></b>
575 :     <p>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; </p>
576 :     <p>The steps for setting up public-key authentication vary
577 :     depending on your SSH client. However, they all follow this set of
578 :     common steps: </p>
579 :     <p>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; </p>
580 :     <ol>
581 :     <li>Use the client program (or a utility that came with it) to
582 :     generate a public/private key pair. This program might be called
583 :     ssh-keygen or puttygen.exe.</li>
584 :     <li>Copy the public key to the server. This is often done by
585 :     pasting the public key into the file <code>/home/user/.ssh/authorized_keys</code>.</li>
586 :     </ol>
587 :     </li>
588 :     <p>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; </p>
589 :     <li><b><a name="ssh_4">When I try to connect using SSH, it tells me
590 :     "Could not chdir to home directory /home/user/myname". What did I do
591 :     wrong?</a></b>
592 :     <p>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; </p>
593 :     <p>This often happens when using SourceForge projects for the first
594 :     time, but may occur on other servers as well. You must manually log in
595 :     to the server, using an interactive SSH session, in order to create
596 :     your home directory for the first time. After this, you will be able to
597 :     log in successfully. </p>
598 :     <p>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; </p>
599 :     <p>Use your SSH client to connect to the server (e.g.
600 :     cvs.sourceforge.net) and log in with your username and password. Your
601 :     home directory will be created for you.</p>
602 :     </li>
603 :     <p>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; </p>
604 :     <li><b><a name="ssh_5">I got an 'Unknown response' while trying to
605 :     perform CVS browsing. What went wrong?</a></b>
606 :     <p>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; </p>
607 :     <p>A problem has been reported that involves the Cygwin SSH client
608 :     (see bug <a href="http://bugs.eclipse.org/bugs/show_bug.cgi?id=21180">21180</a>).
609 :     Try using another SSH client such as Putty or <a
610 :     href="http://www.networksimplicity.com/openssh/">OpenSSH</a>. </p>
611 : jlemieux 1.36 </li>
612 : jlemieux 1.44 <p>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; </p>
613 : james 1.1 </ol>
614 :     <br>
615 :     <!-- Upgrading from Eclipse 1.0 -->
616 : jlemieux 1.43 <h1>Upgrading from Eclipse 1.0</h1>
617 : james 1.1 <ol>
618 : jlemieux 1.44 <li><b><a name="10_1">Is there anything I should do before upgrading
619 :     from Eclipse 1.0 to 2.0?</a></b>
620 :     <p>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; </p>
621 :     <p><b>IMPORTANT:</b> Before upgrading from Eclipse 1.0 to 2.0, make
622 :     sure you release all your changes to the repository using Eclipse 1.0.
623 :     Although it is possible to submit the changes using Eclipse 2.0 after
624 :     you upgrade, to do so is not straight forward due to a change in how
625 :     the synchronization information for each project is stored.</p>
626 :     </li>
627 :     <p>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; </p>
628 :     <li><b><a name="10_2">I'm using a workspace from 1.0. Why does the
629 :     Team menu only contain "Share Project"?</a></b>
630 :     <p>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; </p>
631 :     <p>Team support changed drastically between Eclipse 1.0 and 2.0. As
632 :     such, the method of sharing projects with the repository changed as
633 :     well. We have tried to make it relatively easy for you to migrate,
634 :     however. You will notice that your previously shared projects only have
635 :     "Share Project" in the Team menu. If you select that option, a wizard
636 :     will guide you through the migration process. When you are finished,
637 :     your project will be shared and the Synchronize view will open. You
638 :     will see conflicting changes on every file - this is due to changes in
639 :     the way sync information is stored between 1.0 and 2.0. If you do not
640 :     have any outgoing changes (which you shouldn't have if you committed
641 :     all your outgoing changes before upgrading as recommended above), then
642 :     you can simply select the project in the Synchronize view and select
643 :     "Override and Update" which will load the current contents from the
644 :     server. If you do have outgoing changes, you can pull down the triangle
645 :     menu in the Synchronize view and select "Compare File Contents". After
646 :     some work, the Synchronize view will show you only the files which are
647 :     actually different. You can then use the Synchronize view to resolve
648 :     these conflicts.</p>
649 :     </li>
650 :     <p>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; </p>
651 :     <li><b><a name="10_3">Eclipse 1.0 created all my files as binary in
652 :     the repository. How do I fix this?</a></b>
653 :     <p>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; </p>
654 :     <p>Any file checked into a CVS repository from Eclipse 1.0 was
655 :     marked as binary. This means that end-of-line conversions will not
656 :     occur on checkout, and some features of CVS (such as auto-mergeable
657 :     conflicts) will not apply to these files. As such, it may be desirable
658 :     to change some of these files from binary to text. To change the file
659 :     types, do the following:</p>
660 :     <ol>
661 :     <li>Make sure that all members of your team have saved and
662 :     committed any changes to the affected files.</li>
663 :     <li>Select the resources you wish to change in the Navigator or
664 :     other view.</li>
665 :     <li>Context Menu-&gt;Team-&gt;Set Keyword Substitution...</li>
666 :     <li>Select "Automatic" to use the recommended detection. Click
667 :     Next.</li>
668 :     <li>Select the checkbox labelled "Include files that are already
669 :     in the repository". Click Next.</li>
670 :     <li>Click Finish. All affected files will immediately be modified
671 :     in the repository.</li>
672 :     <li>All other team members must now check out fresh copies of all
673 :     affected files.</li>
674 :     </ol>
675 :     </li>
676 :     <p>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; </p>
677 :     <li><b><a name="10_4">Is a Branch the same as a Stream? What about
678 :     other 1.0 terminology?</a></b>
679 :     <p>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; </p>
680 :     <p>In an effort to move away from generic terminology that applies
681 :     to all repository providers, and toward provider-specific terminologies
682 :     and workflows, many terms, menu items and labels have changed in 2.0.
683 :     Here is a brief list of some of the changes. For more detailed
684 :     information, please see the Eclise CVS documentation.</p>
685 :     <table border="1">
686 :     <tbody>
687 :     <tr>
688 :     <td><b>Eclipse 1.0</b></td>
689 :     <td><b>Eclipse 2.0</b></td>
690 :     <td><b>Comments</b></td>
691 :     </tr>
692 :     <tr>
693 :     <td>Stream</td>
694 :     <td>Branch</td>
695 :     <td>The CVS terminology "Branch" replaces "Stream"</td>
696 :     </tr>
697 :     <tr>
698 :     <td>Catchup</td>
699 :     <td>Update</td>
700 :     <td>"Update" refers to the standard CVS method of retrieving
701 :     remote contents. For more details on Update, see the Eclipse CVS
702 :     documentation.</td>
703 :     </tr>
704 :     <tr>
705 :     <td>Release</td>
706 :     <td>Commit</td>
707 :     <td>These terms are equivalent.</td>
708 :     </tr>
709 :     <tr>
710 :     <td>Add to Workspace</td>
711 :     <td>Check Out as Project</td>
712 :     <td>The CVS terminology "Check Out" replaces "Add to
713 :     Workspace".</td>
714 :     </tr>
715 :     <tr>
716 :     <td><i>None</i></td>
717 :     <td>Tag</td>
718 :     <td>In CVS, a Tag refers to either a Branch Tag or a Version
719 :     Tag. Branches and versions together are referred to as Tags.</td>
720 :     </tr>
721 :     </tbody>
722 :     </table>
723 :     </li>
724 :     <p>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; </p>
725 :     <li><b><a name="10_5">I get a message saying the .vcm_meta file is
726 :     obsolete and should be deleted. Should I really delete it?</a></b>
727 :     <p>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; </p>
728 :     <p>In Eclipse 1.0, meta-information about a project was stored in
729 :     .vcm_meta. In Eclipse 2.0, this mechanism was made more general and the
730 :     data was moved to the .project file. As such, the .vcm_meta file is now
731 :     unneeded. The Eclipse CVS client will warn you of this state by placing
732 :     a warning in the task list. If you still have people on your team who
733 :     are using Eclipse 1.0 for development with your repository, then you
734 :     should not delete the .vcm_meta file. If all members of your team are
735 :     using Eclipse 2.0, then you can safely delete the .vcm_meta file and
736 :     commit the deletion to the repository.</p>
737 :     </li>
738 :     <p>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; </p>
739 : james 1.1 </ol>
740 :     <br>
741 :     <!-- Using Eclipse and CVS for Java Development -->
742 : jlemieux 1.43 <h1>Using Eclipse and CVS for Java Development</h1>
743 : james 1.1 <ol>
744 : jlemieux 1.44 <li><b><a name="java_1">When I check out a Java project from the
745 :     repository, how do I make Eclipse aware it is a Java project?</a></b>
746 :     <p>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; </p>
747 :     <p>Eclipse makes use of information in the .project file to
748 :     determine if a project is a Java project. If the project you have
749 :     checked out does not have a .project file, Eclipse will not mark it
750 :     properly. If you use "Checkout As..." instead of "Checkout As Project"
751 :     in the Repositories view, then you will be given an opportunity to
752 :     specify Java as the project type and provide Java specific
753 :     configuration information.</p>
754 :     <p>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; </p>
755 :     <p>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; </p>
756 :     </li>
757 :     <li><b><a name="java_2">What is the .classpath file? Should I commit
758 :     it to the repository?</a></b>
759 :     <p>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; </p>
760 :     <p>Eclipse's Java development tools create and maintain a special
761 :     file, .classpath, in the root of each Java project. This file contains
762 :     information about the project's classpath, including references to
763 :     other projects, external jars, and the project's own source path. If
764 :     you are working on a team with other developers that use Eclipse, you
765 :     probably want to commit this file to the repository so that others can
766 :     benefit from correct classpath settings. If the other developers on
767 :     your team do not use Eclipse, you may still want to commit the
768 :     .classpath file so that your settings are persisted - this should not
769 :     affect the users that are not using Eclipse.</p>
770 :     <p>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; </p>
771 :     <p>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; </p>
772 :     </li>
773 :     <li><b><a name="java_3">In my CVS repository, there is a source
774 :     directory in the repository root. How can I use this with Eclipse?</a></b>
775 :     <p>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; </p>
776 :     <p>If the name of the CVS module is part of the package name of
777 :     Java files, you will encounter problems. For example, if the module you
778 :     check out is called "test", and it contains a folder called "code"
779 :     which contains Java files that claim to be in the package "test.code",
780 :     Eclipse will not be able to compile these Java classes. There are
781 :     several solutions to this problem:</p>
782 :     <ol>
783 :     <li>One solution is to move the top-level package folder ("test"
784 :     in this case) to be a subfolder of the CVS module. In this case, create
785 :     a folder called "test" in the project "test", and move "code" into it.
786 :     Then commit your changes.
787 :     <p>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; </p>
788 :     </li>
789 :     <li>Another possible solution is to use modules definitions.
790 :     Modules can be defined in the CVSROOT/modules file to include root
791 :     level projects as subfolders of the checked out folder stucture. The
792 :     steps to get this to work for the above example are:
793 :     <ol>
794 :     <li>Add the following two lines to the CVSROOT/modules file<br>
795 :     test &amp;test<br>
796 :     MyProject &amp;test </li>
797 :     <li>In the CVS Repositories View, select the modules with the
798 :     name matching the one defined in the CVSROOT/modules file (Note that in
799 :     Eclipse 2.0.x, you will need to switch to "Show Modules" mode using the
800 :     drop down menu in the title bar in order to see the module).</li>
801 :     <li>Select "MyProject" and choose "Checkout Module" from the
802 :     popup menu.</li>
803 :     </ol>
804 :     See the <a href="http://www.cvshome.org">CVS documentation</a> for
805 :     more information on defining modules.
806 :     <p>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; </p>
807 :     </li>
808 :     <li>If you are using Eclipse 2.1, you can create a new Java
809 :     Project and then perform a "Checkout Into..." on the CVS Module. This
810 :     operation allows you to check out a CVS modules into an existing
811 :     project as a subfolder and configures that target project to be shared
812 :     with CVS. </li>
813 :     </ol>
814 :     <p>Source folders must always begin beneath the project, not above
815 :     it. See the Eclipse Java Development Tools documentation for more
816 :     information on source folders.</p>
817 :     </li>
818 :     <p>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; </p>
819 :     <li><b><a name="java_4">How do I check out a module definition as a
820 :     Java project?</a></b>
821 :     <p>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; </p>
822 :     <p>To check out a module that is defined in the CVSROOT/modules
823 :     file as a Java project, you may have to pre-create the target project
824 :     as a java project in the workspace before performing the "Check Out
825 :     Module". </p>
826 :     </li>
827 :     <p>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; </p>
828 :     <li><b><a name="java_5">Why does the bin directory keep appearing in
829 :     the Synchronize view?</a></b>
830 :     <p>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; </p>
831 :     <p>JDT marks most of its build output as being derived resources so
832 :     that CVS and other repository types can easily ignore these resources
833 :     from version control. However, if you define custom source and build
834 :     output folders, the newly created build output folder will not be
835 :     marked as derived. In many cases the root build output folder is named
836 :     bin. To ignore this folder, select it in the navigator and choose Team
837 :     &gt; Add to .cvsignore, then commit the .cvsignore file to the
838 :     repository so that the bin folder will be ignored at all times for that
839 :     project. </p>
840 :     </li>
841 :     <p>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; </p>
842 :     <li><b><a name="java_5a">I ignored the bin directory but it appears
843 :     to be shared anyway. Why?</a></b>
844 :     <p>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; </p>
845 :     <p>If a resources whose name matches a pattern in the .cvsignore
846 :     also exists in the repository, then this resource is not ignored. For
847 :     the case of the bin folder, chances are that the bin folder was
848 :     committed to the repository at some point. The solution is to purge
849 :     this directory from the repository. </p>
850 :     </li>
851 :     <p>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; </p>
852 :     <li><b><a name="java_6">How do I use CVS keywords in Java templates?</a></b>
853 :     <p>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; </p>
854 : mvalenta 1.51 <p>Substitute the usual keyword (e.g. $Revision: 1.50 $) with the $
855 :     escaped version (e.g. $$Revision: 1.50 $$). </p>
856 : jlemieux 1.44 </li>
857 :     <p>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; </p>
858 :     <li><b><a name="java_7">I'm working with a virtual module defined in
859 :     the CVSROOT/modules file. How do I commit the .project and/or
860 :     .classpath file?</a></b>
861 :     <p>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; </p>
862 :     <p>The easiest way to address this problem is to create a project
863 :     in the repository whose purpose is to hold the .project and .classpath
864 :     files for your module. For example, if your module definition is <i>my-module
865 :     &amp;sub-dir1 &amp;sub-dir2</i> you could change it to <i>my-module
866 :     my-module-project &amp;sub-dir1 $sub-dir2</i> where my-module-project
867 :     is an new folder on the CVS server. Committing the .project and
868 :     .classpath files would create the files in this folder. </p>
869 :     </li>
870 :     <p>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; </p>
871 : james 1.1 </ol>
872 :     <br>
873 :     <!-- Compatibility Between CVS Command-line Client and Eclipse -->
874 : jlemieux 1.43 <h1>Compatibility Between CVS Command-line Client and Eclipse</h1>
875 : james 1.1 <ol>
876 : jlemieux 1.44 <li><b><a name="commandLine_1">Does Eclipse use [WinCVS|CVS
877 :     command-line client] to talk to the server?</a></b>
878 :     <p>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; </p>
879 :     <p>No. Eclipse implements a CVS client in Java that talks directly
880 :     to the server using the documented CVS protocol. No external CVS client
881 :     is required.</p>
882 :     </li>
883 :     <p>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; </p>
884 :     <li><b><a name="commandLine_2">The command-line CVS client stores
885 :     information in CVS folders. Does Eclipse do the same thing? If so,
886 :     where are the folders?</a></b>
887 :     <p>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; </p>
888 :     <p>Eclipse stores CVS sync information in CVS/ folders in the same
889 :     way as the command-line CVS client does. However, you rarely see these
890 :     folders within Eclipse. They are marked using a Core facility called
891 :     "team-private" which causes them to be hidden from view. If you open a
892 :     (non-Eclipse) file explorer you will see that these directories and
893 :     their contents appear on the file system.</p>
894 :     </li>
895 :     <p>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; </p>
896 :     <li><b><a name="commandLine_3">Is Eclipse compatible with the
897 :     command-line CVS client?</a></b>
898 :     <p>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; </p>
899 :     <p>Eclipse Team CVS stores its meta information in a format that is
900 :     compatible with the command-line CVS client. Thus you should be able to
901 :     use a CVS command line client against Eclipse workspace files on disk.
902 :     Please note that this support is experimental, and you may run into
903 :     problems. However, we are very interested in making this work, so
904 :     please report any bugs you find.</p>
905 :     <p>Whenever you use external tools to modify workspace files, you
906 :     must perform a Refresh from within Eclipse to make the workspace aware
907 :     of the changes.</p>
908 :     <p>You may encounter unexpected behaviour when using the
909 :     command-line CVS client in conjunction with deleted folders. Eclipse's
910 :     CVS support keeps track of deleted folders and their contents so that,
911 :     on the next synchronization, the Synchronize view can properly report
912 :     on the changes. This information is kept outside of the CVS meta folder
913 :     structure. This is because in CVS you normally inform the repository of
914 :     deletions prior to deleting them locally, which is a different workflow
915 :     than we like to support in the Synchronization view. Thus it is
916 :     recommended that you do not use the command-line CVS client while you
917 :     have pending deletions to commit. In some circumstances it could cause
918 :     the Synchronize view to display incorrect contents, although it should
919 :     not cause any lost work.</p>
920 :     </li>
921 :     <p>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; </p>
922 :     <li><b><a name="commandLine_4">Can I import a project into Eclipse
923 :     that was checked out using the command line?</a></b>
924 :     <p>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; </p>
925 :     <p>Yes you can. However, you may encounter errors from the builder
926 :     related to the copying of the CVS folders. This can have two causes.
927 :     The first is when the project is imported before the CVS plugin is
928 :     loaded. To avoid this problem, make sure you open one of the CVS views
929 :     before importing the project. The second is due to a "race" on import
930 :     between the CVS plugin and other plugins that react to the import. If
931 :     the CVS plugin wins the race, then the CVS folders are hidden but if
932 :     another plugin discovers the CVS folders first, it may cause the
933 :     workbench to "know" about them and perform inappropriate actions on
934 :     them. The best way to solve the problem is to run a <b>Team&gt;Update</b>
935 :     on the project and then shutdown and restart Eclipse (although closing
936 :     and reopening the view in which the CVS folders appear may work as
937 :     well). If this fails, you may need to check the projects out from your
938 :     repository using Eclipse instead of the command line client.</p>
939 :     <p>There is a plugin named <i>org.eclipse.team.cvs.delta</i>
940 :     available on the <a
941 :     href="http://dev.eclipse.org/viewcvs/index.cgi/%7Echeckout%7E/platform-vcm-home/dev.html">Development
942 :     Resources</a> page that loads on startup and ensures that CVS folders
943 :     are properly hidden. If you import CVS projects often, you may want to
944 :     use this plugin. </p>
945 :     </li>
946 :     <p>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; </p>
947 :     <li><b><a name="commandLine_5">Why does Eclipse corrupt my *.jar,
948 :     *.zip, etc. files?</a></b>
949 :     <p>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; </p>
950 :     <p>This problem is caused by the keyword substitution mode assigned
951 :     to the file on the server. Any binary files must be marked as -kb. The
952 :     default for CVS is to mark unknown file types as text. CVS provides
953 :     cvswrappers and the cvs admin command to set file types.</p>
954 :     </li>
955 :     <p>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; </p>
956 :     <li><b><a name="commandLine_6">When I use the command-line CVS on my
957 :     project, why do the CVS folders sometimes appear in the Navigator View?</a></b>
958 :     <p>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; </p>
959 :     <p>There are some cases where CVS folders are not hidden from the
960 :     UI as the user would expect. For instance, CVS folders will appear if a
961 :     user imports a CVS project into Eclipse before the CVS plug-in is
962 :     loaded. To avoid this, open the CVS Repositories view (thus loading the
963 :     CVS plug-in) before importing CVS projects into Eclipse. There is also
964 :     a plugin available <a
965 :     href="http://dev.eclipse.org/viewcvs/index.cgi/%7Echeckout%7E/platform-vcm-home/dev.html">here</a>
966 :     that will ensure that the CVS folders are properly hidden even if the
967 :     CVS plugin is not loaded.</p>
968 :     </li>
969 :     <p>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; </p>
970 :     <li><b><a name="commandLine_7">When I use the command-line CVS on my
971 :     project, why go I get "resource out of sync" errors?</a></b>
972 :     <p>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; </p>
973 :     <p>This occurs when files that are resources in Eclipse are
974 :     modified outside of Eclipse. One solution is to perform a refresh
975 :     (available from a resource's popup menu) on any resources or projects
976 :     that where modified outside of Eclipse. There is also an "auto-refresh"
977 :     plugin available from Platform Core (click <a
978 :     href="http://dev.eclipse.org/viewcvs/index.cgi/%7Echeckout%7E/platform-core-home/dev.html">here</a>
979 :     to go to there).</p>
980 :     </li>
981 :     <p>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; </p>
982 : james 1.1 </ol>
983 :     <br>
984 :     <!-- Working with Patches -->
985 : jlemieux 1.43 <h1>Working with Patches</h1>
986 : james 1.1 <ol>
987 : jlemieux 1.44 <li><b><a name="patches_1">How do I send someone a patch?</a></b>
988 :     <p>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; </p>
989 :     <p>If you have modified a project that you checked out from CVS,
990 :     you may want to send those changes to someone else. This often occurs
991 :     when you do not have commit rights, but want to send the changes to
992 :     someone who does. To create a patch file:</p>
993 :     <ol>
994 :     <li>Select the changed project in the Navigator or other view.</li>
995 :     <li>Context Menu-&gt;Team-&gt;Create Patch...</li>
996 :     <li>Select a location for the patch.</li>
997 :     <li>Use E-mail or other delivery method to send the patch to
998 :     someone else.</li>
999 :     </ol>
1000 :     </li>
1001 :     <p>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; </p>
1002 :     <li><b><a name="patches_2">How do I apply a patch that someone sent
1003 :     me?</a></b>
1004 :     <p>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; </p>
1005 :     <p>To apply a patch, such as one generated in the previous step, do
1006 :     the following:</p>
1007 :     <ol>
1008 :     <li>Select the changed project in the Navigator or other view.</li>
1009 :     <li>Context Menu-&gt;Compare With-&gt;Patch...</li>
1010 :     <li>Fill in the location of the patch file</li>
1011 :     <li>Click Next. A summary of changed files will appear.</li>
1012 :     <li>Click Finish. The changes are now merged into the workspace.</li>
1013 :     <li>Context Menu-&gt;Team-&gt;Synchronize. You may now commit the
1014 :     changes into the repository.</li>
1015 :     </ol>
1016 :     </li>
1017 :     <p>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; </p>
1018 : james 1.1 </ol>
1019 :     <br>
1020 : mvalenta 1.30 <!-- Linux -->
1021 : jlemieux 1.43 <h1>Linux Issues</h1>
1022 : mvalenta 1.30 <ol>
1023 : jlemieux 1.44 <p>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; </p>
1024 :     <li><b><a name="linux_0">On linux, using IBM JRE 1.3.0, I get a
1025 :     timeout when connecting to a repository. What's wrong?</a></b>
1026 :     <p>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; </p>
1027 :     <p>Problems have been reported in this area using IBM JRE 1.3.0 on
1028 :     Linux. The solution is to upgrade your JRE to version 1.3.1.</p>
1029 :     </li>
1030 :     <p>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; </p>
1031 :     <li><b><a name="linux_1">On Red Hat 8, Eclipse fails to make a
1032 :     checkout but it works with other clients. Why?</a></b>
1033 :     <p>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; </p>
1034 :     <p>The problem may be the encoding in /etc/sysconfig/i18n file. If
1035 :     the language encoding is </p>
1036 :     <pre> LANG="en_US.UTF-8"<br> </pre>
1037 :     changing it to
1038 :     <pre> LANG="en_US"<br> </pre>
1039 :     should fix the problem.
1040 :     <p></p>
1041 :     </li>
1042 :     <p>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; </p>
1043 : mvalenta 1.30 </ol>
1044 :     <!-- Windows -->
1045 : jlemieux 1.43 <h1>Windows Issues</h1>
1046 : mvalenta 1.30 <ol>
1047 : jlemieux 1.44 <p>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; </p>
1048 :     <li><b><a name="windows_0">Eclipse crashed Windows 2000 (blue screen)
1049 :     when performing a CVS operation. What happened?</a></b>
1050 :     <p>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; </p>
1051 :     <p>Instances of this have been reported that involve the NDIS.sys
1052 :     driver and particular brands of network cards (see bug <a
1053 :     href="http://dev.eclipse.org/bugs/show_bug.cgi?id=21276">21276</a>).</p>
1054 :     </li>
1055 :     <p>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; </p>
1056 :     <li><b><a name="windows_2">Eclipse always times out when performing a
1057 :     Synchronize on one or two particular machines?</a></b>
1058 :     <p>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; </p>
1059 :     <p>Instances of this have been reported that involve the VIA
1060 :     on-board network cards (see bug <a
1061 :     href="http://dev.eclipse.org/bugs/show_bug.cgi?id=21276">27077</a>).
1062 :     Changing the network card fixed the problem.</p>
1063 :     </li>
1064 :     <p>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; </p>
1065 :     <li><b><a name="windows_3">Why do CVS operations slow down when I am
1066 :     connected to my network/dial-up?</a></b>
1067 :     <p>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; </p>
1068 :     <p>I have a large number of entries in my hosts file for anti-ad
1069 :     software - and when I'm connected, name resolution (even to localhost)
1070 :     slows to a crawl. When I'm not connected, localhost gets resolved at
1071 :     normal speed. I think this might be a "feature" of 2000/XP - it didn't
1072 :     happen in NT.</p>
1073 :     </li>
1074 :     <li><b><a name="windows_4">Why do all my files show as outgoing
1075 :     changes?</a></b>
1076 :     <p>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; </p>
1077 :     <p>The CVS plugin uses timestamps of the files on disk to track the
1078 :     modification state of versioned files. As a result, there are some
1079 :     cases where Windows users may find that as a result of either (1) an
1080 :     automatic daylight savings change or (2) moving files between file
1081 :     systems, that all the files show up as outgoing changes. See <a
1082 :     href="http://dev.eclipse.org/bugs/show_bug.cgi?id=5337">Bug 5337</a>
1083 :     for an explanation of the problem and workarounds. </p>
1084 : mvalenta 1.50 <p>Thers is a utility action that will reset the timestamps so the
1085 :     files are in-sync with CVS. Be warned however that this utility resets the
1086 :     timestamps for any file whose timestamp differs from the sync timestamp by 1 hour.
1087 :     There is a possibility that this could reset a file that is really dirty. Use at your own risk.
1088 : mvalenta 1.51 To use the action, install the plugin found <a href="http://dev.eclipse.org/viewcvs/index.cgi/%7Echeckout%7E/platform-vcm-home/plugins/fixtimestamps.zip">here</a> and them run the CVS Util/Fix Timestamps command.
1089 : mvalenta 1.50 </p>
1090 : mvalenta 1.38 </li>
1091 : jlemieux 1.44 <p>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; </p>
1092 : mvalenta 1.30 </ol>
1093 : james 1.1 <!-- Miscellaneous -->
1094 : jlemieux 1.43 <h1>Miscellaneous</h1>
1095 : james 1.1 <ol>
1096 : jlemieux 1.44 <li><b><a name="misc_0">Is there any equivalent to CVS_CLIENT_LOG is
1097 :     Eclipse?</a></b>
1098 :     <p>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; </p>
1099 :     <p>Yes, there are tracing facilities in Eclipse that will allow you
1100 :     to see what messages are being communicated between the CVS client and
1101 :     server. Here's how:</p>
1102 :     <ol>
1103 :     <li>Create a file named ".options" in you eclipse directory (the
1104 :     directory that contains the executable) that contains the following 2
1105 :     lines that enable CVS debugging.
1106 :     <pre> org.eclipse.team.cvs.core/debug=true<br> org.eclipse.team.cvs.core/cvsprotocol=true<br> </pre>
1107 :     </li>
1108 :     <li>Start Eclipse with the following parameters tailored to you
1109 :     local setup (The below example is for windows). The important aspects
1110 :     are the use of java.exe instead of javaw.exe and the inclusion of the
1111 :     -debug and -consolelog options. These will cause the debug console to
1112 :     be visible and for debugging output to appear in the console.
1113 :     <pre> C:\eclipse\eclipse.exe<br> -vm C:\jre\bin\java.exe<br> -data C:\eclipse\workspace<br> -debug<br> -consolelog<br> </pre>
1114 :     </li>
1115 :     <li>Inside Eclipse, create your repo location and expand it in
1116 :     the repositories view (for example). The CVS command traffic in the
1117 :     debug console should contains an invocation of the update command that
1118 :     looks something like (this is output from dev.eclipse.org):
1119 :     <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>
1120 :     </li>
1121 :     </ol>
1122 :     </li>
1123 :     <p>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; </p>
1124 :     <li><b><a name="misc_1">What is the .project file, and should I
1125 :     release it to CVS?</a></b>
1126 :     <p>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; </p>
1127 :     <p>The .project file is created and maintained by Eclipse. It
1128 :     stores meta-information about the project, such as which projects it
1129 :     references and what type of project it is. If other members of your
1130 :     team will be using Eclipse to check out this project from CVS, you
1131 :     almost certainly want to release the .project file to CVS. Even if
1132 :     other members of your team are not using Eclipse, you may still want to
1133 :     release the .project file so that the information is persisted for you.</p>
1134 :     </li>
1135 :     <p>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; </p>
1136 :     <li><b><a name="misc_2">I don't have update access to the CVS
1137 :     repository. Can I still check out a project with Eclipse?</a></b>
1138 :     <p>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; </p>
1139 :     <p>In some circumstances, depending on permissions on the server,
1140 :     you may not be able to browse the repository in the CVS Repositories
1141 :     view. In this case, it may still be possible to check out the project
1142 :     you want.</p>
1143 :     <ol>
1144 :     <li>Create an empty project.</li>
1145 :     <li>Context Menu-&gt;Team-&gt;Share Project...</li>
1146 :     <li>Enter the repository information and click Finish</li>
1147 :     <li>The Synchronize view appears. Update all incoming changes.</li>
1148 :     </ol>
1149 :     <p>The project in your workspace is now shared with the CVS
1150 :     repository, and contains the remote contents.</p>
1151 :     </li>
1152 :     <p>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; </p>
1153 :     <li><b><a name="misc_3">What does "Terminated with fatal signal 10"
1154 :     mean?</a></b>
1155 :     <p>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; </p>
1156 :     <p>There is a bug in the CVS server related to some compression
1157 :     levels. If you get this error, change the compression level on the CVS
1158 :     preferences page and see if that helps.</p>
1159 :     </li>
1160 :     <p>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; </p>
1161 :     <li><b><a name="misc_4">I copied some folders from one CVS project to
1162 :     another and the old CVS information remained. What happened?</a></b>
1163 :     <p>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; </p>
1164 :     <p>There is a bug in the CVS client in Eclipse 2.0 that will not
1165 :     purge the CVS folders properly if a folder under CVS control is moved
1166 :     into a folder that is not under CVS control. If this occurs, you will
1167 :     need to delete the CVS folders manually.</p>
1168 :     </li>
1169 :     <p>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; </p>
1170 :     <li><b><a name="misc_8">I used Team &gt; Share Project to connect a
1171 :     local project to an existing project and it takes forwever. Why?</a></b>
1172 :     <p>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; </p>
1173 :     <p>The particular method you have chosen to populate your workspace
1174 :     (i.e. create a new project and then sync against a large existing one)
1175 :     happens to be one of the most ineffiecient operations in the Eclipse
1176 :     CVS client. The CVS protocol does not support this type of operation
1177 :     directly which results in the ineffiecient, communication intensive
1178 :     operation. The proper way to populate your workspace is to use
1179 :     "Checkout as Project" from the CVS Repositories view. Once the project
1180 :     and its contents exists locally, the synchronize operatons should be
1181 :     much faster.</p>
1182 :     </li>
1183 :     <p>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; </p>
1184 :     <li><b><a name="misc_9">Does Eclipse support Watch/Edit?</a></b>
1185 :     <p>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; </p>
1186 :     <p>Eclipse 2.1 supports CVS Edit/Unedit. In 2.0, you can use the
1187 :     following workaround:</p>
1188 :     <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>
1189 :     <p> Unedit works the same as Edit, Editors works the same way as
1190 :     Watchers. To use the tools, highlight the file or directory on which to
1191 :     execute the CVS command, then select Run-&gt;External Tools-&gt;<tool
1192 :     name=""> If you don't select the file/directory first, CVS will
1193 :     complain that the CVSROOT variable must be set first. </tool></p>
1194 :     </li>
1195 :     <p>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; </p>
1196 :     <li><b><a name="misc_12">Why do I get a "Pre-commit failed" error
1197 :     with no detailed error message?</a></b>
1198 :     <p>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; </p>
1199 :     <p> The problem is that the CVS server communicates the error
1200 :     details as M messages instead of E messages and so the error handling
1201 :     in Eclipse doesn't display them. Eclipse has a CVS console which you
1202 :     can open from the Window&gt;Show View&gt;Other menu command. If this
1203 :     view is open and you run the failing commit, it will show you the error
1204 :     details. </p>
1205 :     </li>
1206 :     <p>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; </p>
1207 : james 1.1 </ol>
1208 : jlemieux 1.44 </body>
1209 :     </html>