A SSL security problem implied an SSL upgrade on the amap-dev.cirad.fr SVN server. SmartSVN 6 and 7 can not talk any more to this server. An upgrade to SmartSVN 8 is needed (Windows, Linux and Mac). During the process, the local copy format will be changed from 1.6 or 1.7 to 1.8 (tested successfully under Linux 32 and 64 bits and Windows).
Note if you use several SVN clients: other SVN clients may work normally with the new SSL version, some of them may need an upgrade to recognize the working copy under format 1.8.
Note: Java 1.7 can cause an handshake error during the SmartSVN connection to the SVN server. The workaround is to switch from https:// to http:// (means 'without SSL') and make a new svn checkout. See the related doc, section 3.
Here is a step by step howto.
Launch SmartSVN 8
Open existing working copy
Wait until the upgrade is over. The AMAPstudio or capsis directories will appear in the SmartSVN 'Directories' panel.
Now it is possible again to update your local copy with SmartSVN 8.
The update should be performed. At the end, the 'Output panel' will show the updated revision, e.g. 'at revision 8290'.
You may then recompile with 'ant clean compile' and you should have 'BUILD SUCCESSFUL' (otherwise, tell your favorite developer).
Eclipse users may need to upgrade their SVN plugin. Here is a howto for Eclipse Kepler, the Subversive plugin and the SVN kit version 1.8.
Help > Install new software > add this link if needed: http://community.polarion.com/projects/subversive/download/eclipse/3.0/kepler-site/
Then Eclipse > Window > Preference > Team > SVN > SVN client tab
The subversive plugin in Eclipse should now be compatible with your SVN local copy upgraded in version 1.8.
Follow the instructions here (tested with Ubuntu 13.10): http://sharadchhetri.com/2014/02/05/install-subversion-1-8-on-ubuntu-using-apt/