How to resolve svn: Error setting property 'log':
I was trying to check in some changes on the Model-Glue framework and kept getting this error:
2 At revision 184.
3commit -m "Removed potential recursion in this functionality..." D:/webroot/ModelGlueTrunk/ModelGlue/gesture/helper/HelperInjector.cfc D:/webroot/ModelGlueTrunk/ModelGlue/gesture/helper/IncludeHelperShell.cfc
4 Failed to execute WebDAV PROPPATCH
5svn: Commit failed (details follow):
6svn: At least one property change failed; repository is unchanged
7RA layer request failed
8svn: Error setting property 'log':
9Could not execute PROPPATCH.
I updated from SVN, thinking it to be a synchronization error, but I still got the same error.
I used the 'cleanup' or SVN:clean functionality to maybe get the .svn files and such back in to the right condition, but that didn't help either.
The original SVN Comment I used was:
2Also removed useless cfdump when a helper is attempted to be included but doesn't have a cfc or cfm extension
Can you spot the issue? I can't either. What fixed the error:
2svn: Commit failed (details follow):
3svn: At least one property change failed; repository is unchanged
4RA layer request failed
5svn: Error setting property 'log':
6Could not execute PROPPATCH.
Was changing the multi-line comment to a single line comment. Once the comment was a single line, there was no issue checking it in. I'm not sure what I learned here, but I hope SVN doesn't REALLY have a problem with multi-line comments, after all, we need those to keep details on what changed!
There are no comments for this entry.


Hola, gracias, por sus comentarios; yo puse el comentario en una sola linea y ya no se presentó el problema.
Thanks a lot it worked fine for me as well
Thank you! I could not figure this out for the life of me, I really wanted to keep my pretty print multi line comments, oh well... I removed the line breaks and it worked like a charm.
Thanks a lot this saved me a lot of time.
Regards,
Sendhil
Awesome. Simple but a decisive solution.
Saved a lot of time.
A solution would be (At least with Aptana studio, but should also work with the normal eclipse):
Go to preferences->Team->SVN and change the SVN Interface to SVNKit, that one doesn't seem to have the bug.
Source: http://blog.andrekolell.de/2009/05/18/subclipse-pr...