Future on Rails

Using Rails

Posts Tagged ‘scm


leave a comment »

Subversion is a fantastic versioning system (although there’s all the hype about git (to which I am actually switching now)). In the past I stumbled across two problems I want to share with you (including a solution 😉 ):

The first thing is that my IDE (Eclipse/Aptana) doesn’t support the latest SVN version. I use Subclipse in the latest version, but I sometimes receive errors that can only be overcome by deleting the whole project and checking it out again. Furthermore Subclipse is not compatible with the latest console version of SVN. Why do I use the console version? Because it is easier to include versioning tasks in Ant or Capistrano or to simply type stuff in the console (as it is common when developing RoR). So finally I disconnected all my projects in Aptana and went ahead to only using the console version of SVN. My experience: the console version is as easy to use as Subclipse, once you’ve learnt a few commands. For everyone wanting to work fast and seeking to avoid trouble, I would recommend to use SVN directly via console.

Another problem I had was to remove directories from SVN via the command line tool. Simply deleting the directory and then trying to check in didn’t work, because SVN was missing the .svn data for that directory. I had to google a little bit to find the simple solution: “svn rm <dir>” will remove a directory from SVN, even if it’s already deleted locally.

Hope this helps some of you to avoid some of the trouble I had 😉

P.S.: Oh, a bonus solution I had to google for in the beginning: If you want to add several new files to your existing repository (e.g. those created by a generator), a simple “svn add .” won’t work. What you want to do is use “svn add . –force” to avoid the warnings SVN gives you for all the already existing files :).

Written by Matthias Orgler

May 5, 2009 at 3:34 pm

Posted in scm

Tagged with , ,