I had this error happen to me before many times when using Surefire reports
(with Maven builds). It used to locks files, but it can be just any other
program not closing pipes to open files.
So, can you try to move all staged files elsewhere, just for the sake of
making sure they can be manipulated. I would of course, suspect Eclipse to
lock it's workspace settings files. By the way, just asking - why do you
want to commit it? I also saw Intellij project files in the committed code
- I thought it was an error / omission.
Also, I don't know if this will work on Macs, but can but you could give
this a try:
will show what is using any files staged for commit:
$ svn status | grep -P "^[MAD]" | awk '{ print $2 }' | xargs fuser
If it prints something, it means that file is used by other process
Again, not sure how it works on Macs, but, probably, will work:
fuser -kr ./your/svn/directory/you/are/trying/to/commit
what it does - recursively kills all processes using files in the specified
directory.
Best.
Oleg
