Can I definine automatic property setting at a repository level

[Robert Bune <oi...@sneakemail.com>]

I have recently started evaluating Subversion and think it is an
excellent product, and very different to CM Synergy which I currently
use.  There is a wide range of projects that I need to maintain under
source control for which I plan to setup multi repositories each
containing mmultiple projects.  The nature of some projects suits the
default copy-modify-merge model whereas others require to follow the
lock-modify-unlock model.

For example, developers working on J2EE project may be using Eclipse to
modify Java source, XML and JSP files.  They are happy working in
parallel and willing to accept auto merging or resolve change
conflicts.  Other teams are using a software tool which stores projects
as XML, each project can contain many thousands of XML files, these are
hidden from the user who who is only familiar with the tools IDE and
has no need to understand XML.

Having read the latest 1.2 book I have discovered that I can use the
svn:needs-lock property to enforce the locking model, but I want this
to be automatic for all projects within a given repository.  The book
suggests that automatic properties apply to the Subversion install and
can not be configured at repository or project level, please can you
confirm this is the case and if so please consider it for inclusion in
a future release.

---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org

Re: Can I definine automatic property setting at a repository level

[Joshua Varner <jl...@gmail.com>]

On 9/16/05, Robert Bune <oi...@sneakemail.com> wrote:
> I have recently started evaluating Subversion and think it is an
> excellent product, and very different to CM Synergy which I currently
> use.  There is a wide range of projects that I need to maintain under
> source control for which I plan to setup multi repositories each
> containing mmultiple projects.  The nature of some projects suits the
> default copy-modify-merge model whereas others require to follow the
> lock-modify-unlock model.
>
[snip]
>
> Having read the latest 1.2 book I have discovered that I can use the
> svn:needs-lock property to enforce the locking model, but I want this
> to be automatic for all projects within a given repository.  The book
> suggests that automatic properties apply to the Subversion install and
> can not be configured at repository or project level, please can you
> confirm this is the case and if so please consider it for inclusion in
> a future release.
>
You can use autoprops to automatically add properties to files when
they are imported, but this is a client side option. You cannot add these
properties automatically at the server end, but ou can enforce such
a policy, by rejecting any files with out svn:needs-lock from repos
that require that.

Josh

---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org