[COLUG] Eclipse bug with large directory structure

[Travis Sidelinger]

We had this happen too, but I know what the issue was.  It was the
difference between subversion 1.3 and 1.4 (see below).  I ended up
re-rolling my subversion RPMs again.  Subversion 1.4.3 fixed a compile
bug that was in 1.4.2, and I'm now able to build on SLES9 without
hacking the configure scripts.

http://subversion.tigris.org/svn_1.4_releasenotes.html

WARNING: if a Subversion 1.4 client encounters a pre-1.4 working copy,
it will automatically upgrade the working copy format as soon as it
touches it, making it unreadable by older Subversion clients. If you are
using several versions of Subversion on your machine, you need to be
careful about which version you use in which working copy, to avoid
accidentally upgrading the working copy format. This "auto upgrade"
feature, however, does not occur with the new repository format.


Rob Funk wrote:
> kbroestl wrote:
>> If these are developers (relatively tech saavy people..) that we are
>> talking about, it may be a good idea to train them on the basics of
>> command-line svn and just skip Eclipse and the subversion plug in for
>> repository management entirely.
> 
> Watch out I've discovered another way Eclipse doesn't play nicely... with 
> at least some versions of Eclipse and some versions of svn, once 
> SubEclipse has messed with a workspace, the command line svn may refuse 
> to work with it.
> 
> I wonder how many days until Emacs 22.....
>