Subscribe via RSS
Toggle Submenu
  1. Categories
  2. Recent
  3. Tags
View Replies (4)

Resolved Add svn:needs-lock

  1. How-to
0
Votes
Undo
  1. Sly B
    Sly B
  2. PowerBuilder
  3. Tuesday, 15 January 2019 16:28 PM UTC

Hi All,

Can someone explain me (us) how to use svn:needs-lock property ?

I'm trying to force users to lock objects before modify it, but it doesn't work at all.

My configuration is VisualSVN on the server, PB 2017R3 and TortoiseSVN on client.

Through TortoiseSVN, I put svn:needs-lock on the entire folder containing the sources, then I commit the modification.

In PB, I tried to modify and save an object (without lock it) but it failed with a PB messageBox (see attachments).

Ok it sounds good ! But the problem is that I have the same behaviour and same msg even if I lock the object !

I don't understand why.

Thx for your help.

Sly.

Attachments (1)
2019-01-15 16_58_08-Appeon PowerBuilder.png 2019-01-15 16_58_08-Appeon PowerBuilder.png
  1. SVN
Filering Items in a dddw
read XML element and attribute
Responses (4)
Armeen Mazda @Appeon
Armeen Mazda @Appeon Accepted Answer Pending Moderation
  1. Friday, 1 February 2019 03:45 AM UTC
  2. PowerBuilder
  3. # 1

This issue has been resolved in PowerBuilder 2019.  You can download the beta #2 version on Feb 21, 2019 to verify: https://www.appeon.com/developers/pb-2019-beta.html

 

Comment
There are no comments made yet.
Tom Jiang @Appeon
Tom Jiang @Appeon Accepted Answer Pending Moderation
  1. Friday, 18 January 2019 01:29 AM UTC
  2. PowerBuilder
  3. # 2

Hi Sly,

I tested on PB 2017 R3 with TortoiseSVN. I add this need-lock property to the object source files, it doesn't seem to have any effect. I can still edit and save objects in PB. I understand this is an issue. Our development team will analyze and find a solution. 

In the meantime, can you open a support ticket at https://www.appeon.com/standardsupport/newbug so we can track this issue? And please let us know how did you get the popup message. I don't seem to be able to reproduce that. Thanks!

Regards,

Tom Jiang

Comment
Sly B
  1. Sly B
  2. Monday, 21 January 2019 09:48 AM UTC
Hi Tom, thx for your reply.

Here is the ticket: https://www.appeon.com/standardsupport/track/view?id=2184

I got the popup message in PB when I tried to edit or lock an object after committed the files from TortoiseSVN to VisualSVN. The goal was to propagate lock information to all developers.

Regards,

Sly
  1. Helpful
There are no comments made yet.
Sly B
Sly B Accepted Answer Pending Moderation
  1. Wednesday, 16 January 2019 09:15 AM UTC
  2. PowerBuilder
  3. # 3

Hi Bruce,

Thank you for your quick feedback.

I understand but I thought this issue would be resolved with the 2017R3 version. This is not the case ?
As workaround, we will have to put a lock manually on the objects (I'm sure that it will be a problem and there be conflicts).
After some tests, it works (it is impossible to commit a modification on a locked object - ok, that's what I want) but why is the small padlock only visible on the local copy (of the one who puts the lock) and not on the other local copies (even after an update) ?

Thx

Best regards,

Sly

 

Comment
Sly B
  1. Sly B
  2. Wednesday, 16 January 2019 09:35 AM UTC
We cannot see the lock on VisualSVN Server as well. :(
  1. Helpful
There are no comments made yet.
Bruce Armstrong
Bruce Armstrong Accepted Answer Pending Moderation
  1. Tuesday, 15 January 2019 19:29 PM UTC
  2. PowerBuilder
  3. # 4

That looks like a TortoiseSVN or VisualSVN configuration issue.

The needs lock currently won't work with PowerBuilder because PowerBuilder overwrites the source file without respecting the lock on the file that is placed on it by subversion when the needs lock property is set.

 

 

 

 

Comment
There are no comments made yet.
  • Page :
  • 1


There are no replies made for this question yet.
However, you are not allowed to reply to this question.