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