Re: again: overwriting resource -> deleted and not modified

Mark Phippard wrote:
>> If this feature hasn't been released yet, can I recommend that you scope
>> it as "subclipse:DeferFileDelete"
>
> Why?

Well, for the same reasons you would scope any name in an uncontrolled
global namespace; to avoid name clashes with other users of the
namespace. What if I've already got files with that property defined,
with different semantics?

> Ultimately it comes back to that I just do not see any point in adding
> scoping to a name a like this.

You don't ship Subclipse's packages in the default java namespace. The
same reasons apply to why you should scope any svn properties you define
with unique semantics.

- Marc
Received on Sun Nov 27 04:52:05 2005