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:
- 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?!
- 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.
- 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.
Tags: eclipse, hashing, ivy, ivyde, java, linux, permissions