[svn.haxx.se] · SVN Dev · SVN Users · SVN Org · TSVN Dev · TSVN Users · Subclipse Dev · Subclipse Users · this month's index

RE: Re: Project properties: inheritance vs. copying

From: Hendrik Fuß <hendrik.fuss_at_gmail.com>
Date: Wed, 27 Apr 2011 03:21:44 -0700 (PDT)

> >
> > Why would I want to have the project properties copied if I can rely on inheritance? I find that it makes project maintenance more difficult.
> >
> > Is there a rationale behind the copying function?
> You can rely on inheritance _if_ you have the parent folder checked
> out. If you create a new subfolder, say a new program under the main
> project umbrella, and you don't copy the properties, someone else
> could checkout just that one program without the parent and they would
> not then get the parent's properties.

If that is the reason for copying, then the inheritance mechanism is redundant.

In an umbrella project like that, where I cannot rely on inheritance, all folders must carry copies of the project properties, thus inheritance makes no sense.

In my case I can rely on inheritance, because I can guarantee that the main project directory is always checked out. Thus copying makes no sense. Even worse, it interferes with inheritance by overriding the inherited values.

Having a mixture of the two seems inconsistent to me.



To unsubscribe from this discussion, e-mail: [users-unsubscribe_at_tortoisesvn.tigris.org].
Received on 2011-04-27 12:21:49 CEST

This is an archived mail posted to the TortoiseSVN Users mailing list.