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

Setting “svn:needs-lock” property recursively on a folder in repository

From: mercuryman <mercuryman01_at_gmail.com>
Date: Tue, 3 Nov 2009 11:59:36 -0800 (PST)

Hi,

I am trying to set “svn:needs-lock” property recursively on a folder inside
a repository. One of my project teams needs to be notified to lock the file
before editing it from a particular folder. They want to do this on the
server itself rather than the working copy in eclipse.

I could set this property recursively on all the revisions using following
command

svn propset svn:needs-lock --revprop –r ‘HEAD’ yes –R
file://var/svn/repos1/folder1

(above command is for example, I actually created a small script to
recursively set this property on all the revisions)

I made sure this property set by using “svn propget” command and also
looking at the revision property file in “db” directory. It looks good
there.

When I checkout the folder in eclipse it is checked out in Read/Write mode,
where I expect it to be in Read Only mode. I could not find the reason for
this. I am not able to figure out what wrong I am doing. Can someone please
explain how to set this property on repository & make sure it is inherited
by each new revision automatically?

Any help is greatly appreciated. Thanks in advance

-- 
View this message in context: http://old.nabble.com/Setting-%E2%80%9Csvn%3Aneeds-lock%E2%80%9D-property-recursively-on--a-folder-in-repository-tp26163370p26163370.html
Sent from the Subversion Users mailing list archive at Nabble.com.
------------------------------------------------------
http://subversion.tigris.org/ds/viewMessage.do?dsForumId=1065&dsMessageId=2414205
To unsubscribe from this discussion, e-mail: [users-unsubscribe_at_subversion.tigris.org].
Received on 2009-11-03 21:00:30 CET

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

This site is subject to the Apache Privacy Policy and the Apache Public Forum Archive Policy.