Unreserved checkouts

[Dani]

Hi forum,

We are using ClearCase in combination with EA. Have been working OK for a while. We share a common EAP file, divide the model up into packages that are put under source control. Separately we backup the EAP file twice a day to source control.

I noticed a problem recently that I can't remember happenig with previous versions of EA (using latest 748 build). If a developer has a package checked out and a second developer tries to check out the same package, ClearCase will pop up a dialog asking whether you want to do an unreserved checkout (up to here all normal). Unreserved checkouts allow two people to work on the same file in parallel. Both versions get merged eventually. While this works well with code, we don't allow it for EAP xmi files. Now here's the problem.

If one either answers No to the unreserved checkout dialog or cancels out of it, EA forces an import of the latest version of the package that was checked into the source control repository. The problem is that this behaviour undoes all the changes in the EAP file that the first developer made.

Is there a way to stop EA causing an import when cancelling out of that dialog ?

[Martin Terreni]

let me see if I understand it right:

1) we have a developer with unreserved checkeout version opened by him.
2) another developers wants to open it too, so he gets the "unreserved/reserved" dialog.
3) he chooses reserved (or cancels) and then both (?) developers get lates checked in version?

do I get it right?

I have been working with EA and CC for some month and I have to tell you it is very frustrating (mainly becouse of CC). but maybe if I get it right I might have an idea for you.

[Dani]

Martin,

The problem is:

1) Developer 1 checks out a package (reserved) and makes some changes
2) Developer 2 attempts to check out same package. The dreaded "unreserved" checkout dialog pops up.
3) Developer 2 says No or cancels out of the checkout.
4) EA reimports last checked in version of package
destroying all changes Developer 1 had made.

I have an open call with suport and they are working on it. As a workaround we force people to answer yes to the unreserved checkout and then make sure one of the two developers does a check in before proceeding.

WRT your comments on EA/CC, up till I came across this issue we have been working fine with it. Don't find it that frustrating.

[Martin Terreni]

AFAIK you can't check tou same element twice reserved in both.
Any way my guess would be that CC is the problem here. EA only calls CC clients functions (you can see whenever you checkout/in something you get CC dialogs).
Try to check it with Rational.

[Dani]

That's the whole point of a reserved checkout.

[Dani]

Just to let folks know that the latest 750 build fixes the issue.

Thanks Sparx !!