|Re: Subclipse SVN Check In [message #774276 is a reply to message #774246]
||Tue, 03 January 2012 16:16
| Russell Bateman
Registered: July 2009
Location: Provo, Utah, USA
On 03-Jan-12 08:26, Michael Mising name wrote:|
> I have installed the Subclipse Source Control Plugin, and all seems to
> be working fine. But there is one thing I cannot seem to figure out,
> that being how to check a file in? As it stands now, my system will
> allow me to edit a file at any given time, there seems to be no way for
> me to lock a file so that it is read only.
> How do I "check in" a file so that other users (and myself) cannot edit it.
Unless I've misunderstood what you're saying, the answer is that this is
not how Subversion works traditionally.
One checks out new source code locally (svn co), updates that source
code locally whenever someone else has changed it (svn update), and
modifies it without "reserving" it in any way whereupon one commits any
changes made (svn commit). If someone has in the meantime edited and
committed the same file, one must merge changes with what was committed.
Since Subversion 1.2, it has been possible to set an "svn:needs-lock"
property on a given file to restrict it from being edited (and it gets
checked out read-only). Then, you can (must) use svn lock, made edits
and finally commit the file.
I don't know that Subclipse supports this functionality, not having used
I hope this reponse has not been a total waste of your time. There is a
specific Eclipse tools subversive forum in which you could ask this
question even though subclipse and subversive are not the same time, but
that forum is full of (much more) knowledgeable respondants (than I).
Powered by FUDForum
. Page generated in 0.01548 seconds