Posts Tagged ‘eclipse’

Subversive Bug – Too many SVN projects from one source breaks it

Wednesday, October 28th, 2009

Been using Subversive as part of Eclipse for a while now, and it’s generally been good to me. Today, however, I ran across a funny problem when I attempted to check out a new project from the company repository:

Could not set property: org.eclipse.team.svn location. Value is too long.

Which was a little… odd, as I couldn’t recall changing anything in Eclipse that could have caused that. Our SVN repo is located on a server with a very short name, and the paths I was checking out were all < 50 characters. Very strange.

Eventually found this bug, but not until after I’d filed one of my own (since it didn’t come up on a Google Search for some reason), and it basically amounts to concatenating the paths of all the projects pointing a particular repository in a particular workspace together, far as I understand it. Damned if I know why they thought that was a good idea, but there we go. That was in turn resulting in a property exceeding the 4096 character limit Eclipse imposes on them… Buh. You’ll probably need the latest release (0.7.8.I20091023 at the time of writing) in order to fix it. If you can’t upgrade, then you have two solutions: Delete some of your existing projects, (maybe…), or create a new workspace.

Unhelpful Error Messages

Wednesday, October 28th, 2009

Trying to update one of our projects to use the Ivy [1.0.0,) syntax for finding dependencies today, and discovered a few fun facts about Linx and Ivy:

  1. Despite having read/write permissions to a directory, I can’t actually change it’s permissions. Bugger. So what do I do? I copy the directory (so I’m the owner…), then delete the original directory, then rename my one back. What the hell is the point of not letting me change the permissions?!
  2. Ivy would appear to include information like the File’s owner it its hash of the file. I’m not 100% sure on that, but it would seem to be the case, as I made no changes to the ivy.xml file I was working with, just copied it around a little.
  3. IvyDE provides an absolutely useless error message: “Can’t resolve Dependency org#name;rev”. Wonderful. Why can’t you resolve it? At first, it was because the permissions on the server were set incorrectly (remember, you need execute (+x) permissisons to list a directories content…), then it turned out that the hash had failed. Now, IvyDE can’t do much about the first one, as it couldn’t even see the 1.0.1 directory. However, it could have told me that the hash had failed. Would have saved me a fair bit of time. I only found out because I ran the build on the command line… Trivial to fix once I realised the problem, but still annoying.

So yeah… That wasn’t exactly fun.