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
Received on Fri Sep 16 13:16:11 2005