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

View: New views
2 Messages — Rating Filter:   Alert me  

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

by mercuryman :: Rate this Message:

Reply to Author | View Threaded | Show Only this Message

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 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-tp26157883p26157883.html
Sent from the Subversion Users mailing list archive at Nabble.com.

------------------------------------------------------
http://subversion.tigris.org/ds/viewMessage.do?dsForumId=1065&dsMessageId=2413969

To unsubscribe from this discussion, e-mail: [users-unsubscribe@...].

Parent Message unknown Re: Setting “svn:needs-lock” property recursively on a folder in repository

by Ulrich Eckhardt :: Rate this Message:

Reply to Author | View Threaded | Show Only this Message

On Monday 02 November 2009, mercuryman wrote:
> 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.

This sounds weird. Normally you always need a working copy to perform some
work.

> 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

Ahem, I don't think that 'svn:needs-lock' is a revision property (--revprop).

> 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.

If properties and revision properties live in different namespaces, the
revision property would not cause the file to become read-only on checkout.

Uli

--
ML: http://subversion.tigris.org/mailing-list-guidelines.html
FAQ: http://subversion.tigris.org/faq.html
Docs: http://svnbook.red-bean.com/

Sator Laser GmbH
Geschäftsführer: Thorsten Föcking, Amtsgericht Hamburg HR B62 932

**************************************************************************************
Sator Laser GmbH, Fangdieckstraße 75a, 22547 Hamburg, Deutschland
Geschäftsführer: Thorsten Föcking, Amtsgericht Hamburg HR B62 932
**************************************************************************************
           Visit our website at <http://www.satorlaser.de/>
**************************************************************************************
Diese E-Mail einschließlich sämtlicher Anhänge ist nur für den Adressaten bestimmt und kann vertrauliche Informationen enthalten. Bitte benachrichtigen Sie den Absender umgehend, falls Sie nicht der beabsichtigte Empfänger sein sollten. Die E-Mail ist in diesem Fall zu löschen und darf weder gelesen, weitergeleitet, veröffentlicht oder anderweitig benutzt werden.
E-Mails können durch Dritte gelesen werden und Viren sowie nichtautorisierte Änderungen enthalten. Sator Laser GmbH ist für diese Folgen nicht verantwortlich.
**************************************************************************************

------------------------------------------------------
http://subversion.tigris.org/ds/viewMessage.do?dsForumId=1065&dsMessageId=2414041

To unsubscribe from this discussion, e-mail: [users-unsubscribe@...].