To sum up in one sentence, restore first, then update, then modify and submit, OK
svn: Item is out of date
The following error is encountered when using Svn to submit:
Deleting E:/bdf-d7/bdf-dorado7/src/com/bstek/bdf/d7/cms/dir
Item is out of date
svn: Commit failed (details follow):
svn: Item '/trunk/bdf-dorado7/src/com/bstek/bdf/d7/cms/dir' is out of date
The reason for this error is that the local resource file version is not the latest version on the server, so when the local file is modified and then submitted, an Out of date error will be reported.
The solution is that when modifying the file, you must first ensure that it is consistent with the server, and then modify it; at this time, you need to restore the local file (remember to back it up), and then update it to be consistent with the server before modifying it.
http://stackoverflow.com/questions/2805546/svn-item-folder-is-out-of-date
Whenever you see "out of date" in an error message it means that the revision of the item in the repository is newer than the copy in your local working copy.
The solution is always going to be to run an update, so that your working copy is up to date with the repository, and then do the commit again (assuming that the update did not generate any conflicts).
For files, this is usually pretty easy to understand how and why this happens. However, Subversion also versions folders, and it is usually with folders that this problem most often happens.
Subversion does not allow you to delete/rename a folder OR change its versioned properties, UNLESS the local copy of the folder is at the HEAD revision of the folder in the repository.
Your next question might be:
"OK, I can maybe understand that, but why is my folder out of date? I am the only person working in this repository."
That is a valid question, the answer lies in the way that Subversion works.
When you commit a change to a file, the revision of the file in your working copy is updated to that new revision when the commit completes, however the version of the parent folder(s) of that file is not updated.
This is because there may have been adds/deletes to other files in that folder and until you have run an update, the folder is not really at that new revision.
This is called "mixed revision working copies".
In summary, the answer is always to do an update so that the folder or file is updated to its HEAD revision.