Book a Demo

Author Topic: Version Control and and shared packages  (Read 3915 times)

armin

  • EA User
  • **
  • Posts: 63
  • Karma: +0/-0
  • mission possible
    • View Profile
Version Control and and shared packages
« on: January 16, 2007, 03:00:32 am »
Hello,

We have 2 EA-Projects "P1" and "P2". Both of the projects share one package named "common". We put "common" under Version Control. We open "P1", check out "common" and add a class to a diagram. Now we close "P1" and open "P2". The package "common" which is also used by this project is marked as checked out. If we would execute a checkin on Package "common" now, we would loose any change we made in "P1".
(see http://www.sparxsystems.com.au/cgi-bin/yabb/YaBB.pl?board=general;action=display;num=1168870718 )

I think this is a big methodic gap in EA because it strongly restricts the use of shared components in a complex software environment.

Our suggestion is that a checkin should only be possible in the EA-Project were checkout was made. So if user "U1" checks out package "common" in "P1", the checkin can be made only in project "P1" by user "U1".

We appreciate any short term solution for our problem.
Thanx in advance Armin.

« Last Edit: January 16, 2007, 03:01:13 am by armin »