Because it was painful (I have yet to find a good reference guide for Eclipse) I would like to share my experiences here. Please feel free to add there yours, or correct my observations. Also, there are "more ways to do" in Eclipse (but not as many as in Perl ) so the steps described below may not represent the only way, and I do not claim that are the most efficient - but TGT (The Good Thing) is that they work.
jMoby is just like any other Ant-based Java project. It has its own build.xml and it has many nicely-tuned Ant's targets that we would like to continue to use when we put it into Eclipse. The problem how to incorporate an existing project (an Ant-based project) into Eclipse is documented many times, even in the Eclipse help system itself. The problem is that most of these descriptions are not detailed enough, or they do not reflect exactly goals we would like to achieve. So, what are these goals...
For read-only, use an anonymous access::ext:firstname.lastname@example.org:/home/repository/moby
In both cases, you are interested in module moby-live/Java.cvs -d :pserver:email@example.com:/home/repository/moby
By the way, the best CVS client for Windows I know is CVS Tortoise.
You can change the workspace either from File -> Switch Workspace, or by starting Eclipse with a command-line argument -data <directory-name>. If you use more workspaces, it is useful to start Eclipse always with a command-line argument -showlocation - then the path of the current workspace is shown in the window title.
As JMoby uses Maven we need to enable Maven in Eclipse. The Maven plugin requires two other plugins which we need to load.
Help -> Software Updates -> Find and Install -> Search for new features and install will open a dialog which shows all existing update sites your Eclipse already know.
For each of the plugins please open New Remote Update Site and add the following sites and install them (make sure that you unselect optional components of the plugins if they produce errors):
Important: selecting ext means that an ssh protocol will be used to get to the CVS repository. So you need to have an ssh client on your machine to do so. You can use a separate client, or the one which is embedded in Eclipse. By default, Eclipse is looking for an external program called ssh - which it usually finds on Unix systems but not on Windows. That's why on most Windows machine you need to explicitly tell Eclipse to use its own embedded client (the client is called extssh but you could not put it directly in the CVS location definition because it would prevent you to use CVS operations outside of Eclipse). So do the following: Window -> Preferences -> Team -> Ext Connection Method, check Use another connection method type to connect, and select extssh.
Type a project name (I use jMoby), check Create project from existing source, and type the name of a directory where you have checked-out your jMoby local copy.
Now you have jMoby data loaded in - and you may see many problems (in the bottom window). This is because Eclipse does not know yet enough about where jMoby has things and how it uses them. But before we fix that let's do one more thing...
Double-click on install. It shows progress in the bottom of the screen in a console window. After that you may Refresh your workspace.
By the way, from now, you can use any listed Ant target by double-clicking. This is almost the same as you would invoke the Ant from a command-line. More about individual targets is elsewhere in the jMoby documentation (e.g. about general targets, or about Moses).When the task is finished, double-click on initeclipse, which will generate the file pom.xml which the Maven plugin requires to work correctly. After the task refresh your workspace and right-click on the project Maven -> Enable Dependency Management. This will now tell Eclipse to use the maven repository for the build path.
Either outside of Eclipse: add it to the environment variable PATH (a usual way). Or inside Eclipse (but here I know only how to set it for an individual project, not generally): Run -> External Tools -> External Tool -> Ant Build -> jMoby build.xml, select tab Environment -> New, and create a new environment variable PATH and give it directory where is javadoc, e.g. c:\Program Files\Java\jdk1.5.0_05\bin.
Once you have them in build/run you can run them from Eclipse (as always with external scripts, you type more the first time you use a script, but Eclipse remembers it and the next time you will see already your script name in a menu): Run -> External Tools -> External Tools -> Program -> New. Name it (e.g. run-cmdline-client), and Location -> Browse Workspace to select it (in our example find and select build/run/run-cmdline-client.bat). Most of these scripts have an option -help - so put it in Arguments - and change it each time you wish to invoke them with different arguments.
And, of course, for us, dinosaurs, change Windows -> Preferences -> General -> Keys -> Modify -> Schema to Emacs.