Subversion 101: To lock or not to lock..

I am the new guy on a young project.. the project has 10 -> 15 Java
developers. The app is a JBoss app that implements the JBoss Portal
(kinda like a Java version of PHPNUKE).

The project is only a few months old and the project is constantly
changing.. very much in flux.

Here is the problem, I am the SCM on the project and I am telling
everyone based on my experience no one should be locking of any files
(text) on check out. Everyone else on the project is insisting that
some files should be locked on check out.

I showed everyone THE page in the official manual and they don't seem
to care. I shared my previous expereiences on other projects and that
didn't move them. Their line is this: In the new way of fast paced
Java web programming.. you are going to have a ton of conflicts and
merges all the time and it thus it doesn't lend itself to the
'non-locking' way of using Subversion.

Does anyone have any advice for what I should say or how to handle
this situation?

Or.. is their anyone out there using a locking model when working on a
Java web project?

thanks!

-- 
<admiral>
Michael F. March ----- mmarch_aaattt_gmail.com
          "Seriously" - HSR
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org