Bulk modify properties

[GoogleCodeExporter]

What steps will reproduce the problem?
1. Within a repository, many files will be added which contain the "executable" 
(or another) flag set accidentally.
2. Selecting the Properties shelf will show which properties are set (if any)
3. Highlighting multiple files and trying to remove the "executable" flag will 
only succeed if ALL the selected files have that property set. If any do not 
have "executable", the operation fails.

What is the expected output? What do you see instead?
1. svnX should continue through ALL selected elements and remove the 
"executable" property, even when some fail (because they did not have this 
attribute).
2. This would apply to other properties as well, besides just "executable".

What version of the product are you using? On what operating system?
- svnX 1.3.1 for OS X 10.6 (Snow Leopard)

Please provide any additional information below.
- If there are some properties that do not apply to particular items 
(svn:ignore does not apply to files; it applies to folders, and svn:mime-type 
does not apply to folders; it applies to files), it would be nice if svnX could 
"skip" those during a batch modification.

Original issue reported on code.google.com by online...@gmail.com on 12 Aug 2011 at 5:08

[GoogleCodeExporter]

This does work if you enable the 'Call Subversion libraries directly' 
preference.
However, if svnX is using the svn CLI tool then it is as you stated.  (Due to 
the fact that the tool fails.)
So, svnX should, at the very least, report an error, but it would be better if 
I can get it to achieve the same functionality using the svn tool as calling 
the libs directly.

With regard to properties and files vs folders - svnX should/does currently 
correctly apply known properties only as appropriate.  Or can you give a 
specific example where it doesn’t?

Original comment by chris...@gmail.com on 12 Aug 2011 at 6:33

• Changed state: Accepted

[GoogleCodeExporter]

SvnX 1.3.2 now displays an alert if setting or deleting Subversion properties 
fails.
However, deleting non-existent Subversion properties via the CLI no longer 
fails since Subversion 1.7.

Original comment by chris...@gmail.com on 1 Jan 2012 at 7:11

• Changed state: Fixed