Book a Demo

Author Topic: Problems about version control  (Read 5142 times)

Murat S.

  • EA Novice
  • *
  • Posts: 2
  • Karma: +0/-0
    • View Profile
Problems about version control
« on: December 22, 2009, 08:44:40 pm »
I am trying EA for a couple of days in order to decide whether to use it for a small team or not. And I have some problems with version controlling logic that EA use.

I set up the environment so that developers work on their local copies and put packages in the model under version control. I am using TortoiseSVN as VC software. As a team we want to be able to draw sequence diagrams sepeartely. I create logical packages that will contain sequence diagrams and put them under version control too. The problems are:

1) When I want to draw sequence diagrams and check out the sequence diagram package, the classes i have use in order to draw the sequence are also locked and no other collegue can draw sequence diagram using that class. This behaviour comes weird to me so i decided to ask the issue on this forum. Is there a way to change this behaviour?

2) I create nested packages for the sequence diagrams and put them under version control seperately. EA allows me to check out the outher package and my collegue to checks out the inner package seperately. The problem is when my collegue wants to check in his package, a warning appears saying the inner package is already checked out by me. Is this a bug or am i missing something?

Geert Bellekens

  • EA Guru
  • *****
  • Posts: 13523
  • Karma: +574/-33
  • Make EA work for YOU!
    • View Profile
    • Enterprise Architect Consultant and Value Added Reseller
Re: Problems about version control
« Reply #1 on: December 22, 2009, 09:17:22 pm »
Murat

1) I think you can avoid that by creating objects as lifelines in the sequence diagrams rather then using the classes. (hold down the Ctrl button while dragging the class to the diagram and EA should present you with an option to create an object of that class rather then an link to the class.)

2) First thing you need to check is whether you are using "use stubs for nested packages" in your version control setup.
If you are then I consider this a bug and you can report it using the link on the bottom of the page: Report a Bug

Geert

Murat S.

  • EA Novice
  • *
  • Posts: 2
  • Karma: +0/-0
    • View Profile
Re: Problems about version control
« Reply #2 on: December 22, 2009, 10:41:23 pm »
Thanks for your quick response, it was really useful for me.

I am done with (1)

2) In VC configuration "use stubs for nested packages" option is checked. So it seems to be a bug.


David OD

  • EA User
  • **
  • Posts: 56
  • Karma: +0/-0
    • View Profile
Re: Problems about version control
« Reply #3 on: December 23, 2009, 09:35:28 am »
Quote
I am using TortoiseSVN as VC software.

The EA Help indicates that Tortoise SVN is not supported as it is a shell extension.  We had to use something else (SlikSVN).

Hope that helps.
Regards
David

Geert Bellekens

  • EA Guru
  • *****
  • Posts: 13523
  • Karma: +574/-33
  • Make EA work for YOU!
    • View Profile
    • Enterprise Architect Consultant and Value Added Reseller
Re: Problems about version control
« Reply #4 on: December 23, 2009, 06:20:22 pm »
David,

I don't think that is the problem. If Murat can checkin/out then that means that the configuration is fine.
The error he's getting is a plain EA bug.

Geert

HowardB

  • EA Administrator
  • EA User
  • *****
  • Posts: 55
  • Karma: +0/-0
  • I love YaBBies!
    • View Profile
Re: Problems about version control
« Reply #5 on: January 05, 2010, 06:16:20 pm »
To Geert -
Kudos to you for solving problem 1, using Object Instances on Sequence Diagrams.  You are also correct that Murat must be using a Subversion command line client with EA if he has been able to apply version control to a package.  In fact, you cannot even save a VC configuration unless you have correctly specified your Subversion client.

To Murat -
I believe you have wrongly described your problem...
The only time that the message
 "The selected package cannot be checked-out at this time.
   It is currently checked-out in this model, by user 'MuratS'."
can be shown, is when attempting to CheckOut a package.  
It will never be shown when attempting to CheckIn a package - it simply isn't in the code path when checking in!

EA records within the package data who has checked-out a package.  This becomes significant when using a Shared Model deployment.
However, if you make a copy of an EAP file when a package is checked-out to you, then distribute that file to another user, the package is still marked within the EAP file as being checked-out to you, irrespective of the status of the associated XMI file.

The current release of EA has a command for resynchronising the package status with the VC provider.  That should resolve the problem for you.

best regards,
Howard.
« Last Edit: January 05, 2010, 06:17:35 pm by HowardB »