On Wed, Jul 31, 2013 at 11:19 PM, Markus Schaber <m.scha...@codesys.com> wrote: > Using another property is not compatible with inheritance, as it will be > difficult to override the setting again in deeper nested directories. > > What about disabling the feature when the property contains the test "false"?
+1 Inheritable properties need to behave more like the boolean support in our config rather than the existing property boolean support. I.E. explicit true and false values with a default value if a value isn't specified. I think it'd be best to introduce this new style of boolean property only to new svn: properties that we add. Leave the existing ones as empty or "*" (actually any value but it's folded to "*" by our client). This avoids any breakage with existing users, though I really don't expect that anyone would set the value to "false" expecting it to be treated as true.
