I have used VSS under windows to control my source code or
team's development, so I am thinking to control my Java source code
under Linux. Well, CVS is good stuff to apply. My linux system has
installed that, plus, Eclipse supports its management. So i don't need
know those command line for CVS.
Following are my step to use CVS in Eclipse:
1. create the root folder for my CVS modules:
for example: /home/usrname/cvs/CVSROOT
and add a variable environment for CVSROOT in .bashrc script
2. create a folder under CVSROOT for module that to be imported
3. use Eclipse wizard to add CVS repository: start Eclipse:
File --> New --> Projects ... --> Checkout Project from CVS
--> Create a new repository location --> Enter Repository
Location information [Host, Repository Path, User, Password, Connect
Type(I use extssh here)] --> if host connected sucessfully, it will
show all modules under CVSROOT folder, the empty folder created in step
2 will be seen, select that one, click next to add a new project under
your current workspace.
4. if the repository has been created, you can use Eclipse
checkout wizard (like step 3) to use existing repository location to
select one, and then select visible modules under this location,and
then check out as a project in the workspace
5. choose any tag for check out
6. now, these is only a blank project (both client and
server) under your workspace, right click project name in Package
Explorer --> import... --> File system --> import those source
code you want to put into server and check out for client users
7. Synchronize with server (commit source code to server): right
click project name --> Team --> Commit... --> edit some
scripts for committing..
8. Well, the source code has been in both server and client (under
your own workspace folder), for further changes or modifcation of
source code, just need synchronize between client and server.
reference:
http://www.fluidthoughts.com/howto/cvs/
http://help.eclipse.org/help30/index.jsp?topic=/org.eclipse.platform.doc.user/reference/ref-40a.htm
P.S. for internal in our company, we still use
Perforce to control our source code