Mark,
How do I turn off using the Subversion lock feature? I don't want to use
that because I intend to use optimistic collision detection and merge. I
couldn't find a preference to not use this locking feature.
"Mark Phippard" <markphip@gmail.com> wrote on 01/16/2007 09:35:07 AM:
> On 1/16/07, Jim Amsden <jamsden@us.ibm.com> wrote:
>
> I'm editing a model using RSA 7 and Subeclipse. Certain model
> editing operations, but not all, result in a Lock dialog popping up
> requesting a comment to be entered on the model (.emx file) as the
> resource to be locked. Entering a comment and pressing OK results in
> the following error:
>
> lock -m "" D:/workspaces3.2/BDD for SOA/org.omg.uml.services/org.
> omg.uml.services.emx
> RA layer request failed
> svn: Lock request failed: 423 Locked
(https://dev.enterprisecomponent.com:9992
> )
>
> Why am I getting this lock request? I'm working in an eclipse
> workspace with the resouces optimistically checked out. I shouldn't
> be holding any lock until I do the checkin. And why is the lock
> failing? I am connected to the the SVN repository and can browse
> with the SVN Repository Explorer. The .emx resouce appears to be
> locked when as menu item Team->Unlock is selectable in the Project
> Explorer, but lock is not.
>
> It looks like SVN thinks I don't have the lock and someone else
> does. I tried unlocking and relocking the resouce. That appeared to
> work ok (no errors in the Console). But the next model change popped
> the dialog back up again.
>
> In any case, the changes to the model appear to be applied as long
> as I press ok on the lock request. The dialog is just unexpected and
> popups up a lot makeing modeling less convenient.
>
> The lock dialog popping up for RSA users is a known issue that has
> been fixed and will be in the next release (hopefully next week).
> The fact that you get this LOCK error sounds like some problem in
> your end ... maybe with a proxy. If you do not intend to use the
> Subversion lock feature then I would not waste too much time trying
> to fix that.
>
> --
> Thanks
>
> Mark Phippard
> http://markphip.blogspot.com/
Received on Tue Jan 16 20:18:20 2007