Forums

We've upgraded to Jade 6.3 and found the new feature being able to check out a method in multiple deltas appealing. However we found a major problem when the person who checked in their changes to a method first found them not there after the second person checked in their modifications. Each delta held only the changes the current user had made to the method.

There doesn't appear to be any checking or warning that the method source has been modified by another user when the second user goes to check in their changes. The checked in changes aren't visible in the second delta - presumably one of the indicators there will be a problem with the check in.

In a multi-developer environment this makes this feature practically useless as the risk of losing previously checked in modifications means that we will be implementing the ini file setting to limit to single delta checkout immediately. It would be great if Jade were able to implement conflict detection as a minimum and preferably the checked out changes picking up any changes made to the method outside of delta.

Hi Chris,

Thanks for your posting. We've tried to reproduce this behaviour but at the point of user one attempting to check the method in they're presented with a message dialog that warns "Cannot check in/out - object(s) locked by other user(s)".

Can you please tell me, what version of JADE 6.3 you're using?

Thank you,

Hi,

Thanks for the reply. We are using 6.3.05 and I am able to reproduce this in a empty system (with 1 new schema) by creating a JadeScript method and checking it out with one user in a delta and updating then logging in as another user and checking out in another delta and modifying the method. Logging back in as the first user I check the method changes in the first delta and then as the second user check in the second delta changes overwriting the first user's modifications. No warnings at any point.

Thanks,
Chris

Hi Chris, did you even manage to make any progress with this? Im using JADE 6.3.08 and I'm seeing the same issue you reported, in that when checking in a method that was modified under another delta there is no merge conflict on check in.

- Dr Danyo.

We specifically disable the ability to check out a method to more than one delta - doing so breaks our development lifecycle.

Belatedly - we turned off the option to prevent multiple check-outs.

I have just come across the same problem. It seems the multi delta setting is pointless, why even have it if 1 check in can override the other?