It may be tricky to install correctly the SVN plugin and connectors in Eclipse. This is an installation proposal, other options may be chosen.
This was done on Linux Ubuntu 11.04 64 bits edition but it should be ok for other systems.
Note: use the last Eclipse version: e.g. Kepler (24.4.2014). Check that you select the correct SVN version, e.g. SVN 1.8 (24.4.2014).
An Eclipse SVN plugin is mandatory
Eclipse should always be used with a SVN plugin installed, even if the SVN commands are passed from another SVN client (Tortoise under Windows, SmartSVN or the terminal). Otherwise, the refactoring actions (rename, move files) would not be stored and would be forgotten when comitting (commit can be done from every SVN client), resulting in an incomfortable result (renamed or moved files considered missing and re downloaded from the server…).
1. Install Eclipse (download the last version for Java developers, Neon is a working release with Subversive available (see below))
2. Install the SVN plugin
If the Subversive entries are missing
For new versions of Eclipse, the Subversive entries may not exist (example: for Eclipse 2018-12, when choosing Eclipse > Help > Install New Software > Work with: '2018-12 - http://download.eclipse.org/releases/2018-12', the 'Collaboration' entry contains no entry related to 'Subversive'). In that case:
If the Subversive Connector Discovery is not proposed
Window → Preference → Team → SVN click > SVN Client > Get Connectors.
Warning: if the SVN connectors are not installed, it might be impossible to tell Eclipse the project is under SVN version control lower.
If the Subversive SVN Connector Discovery dialog appears at each Eclipse launching
Install the SVN kit connector manually :
3. Create your project in Eclipse
Two choices: if you don't have yet a local copy and you'd like to checkout directly with Eclipse, see section 3.1. If you already have a local copy and you want to open it in Eclipse, see section 3.2.
3.1. Checkout your project
Optional: tell Eclipse this is a Java project (fc-24.4.2014).
In some cases, the upper process is not enough to make Eclipse understand that this is a Java project, to be built with Java (the project can not be built: Project > Build project is disabled).
In this case, you may try this way:
After this procedure, your project should be recognized by Eclipse as a Java project AND a SVN project.
3.2. Add an existing local copy in Eclipse
If you already have a local copy of Capsis, you may add it as a project in Eclipse:
Then, to tell Eclipse the project is under SVN:
Check your SVN plugin
If the SVN plugin is not installed well in Eclipse, refactoring (renaming, moving in another package) a class in Eclipse will not be understood at commit time (resulting in 'missing' classes and duplicate classes coming back with the original name or location on SVN update).
To check the SVN plugin installation is Ok, try this:
If SmartSVN does not not detect the name change, you can not use the Refactor tool in Eclipse to rename or move classes. You must first complete the svn plugin correct installation. Check particularly the SVNkit connectors installation upper.
4. Configure the project
See: http://capsis.cirad.fr/capsis/documentation/code_editor, section Eclipse > Build Capsis.