Shared packages

[armin]

Hi,

we choose a component oriented architecture for implementing our SW-products. As a result our system consists of common components and domain specific components.
Every product corresponds with one EA-Project. The common components used by multiple EA-projects.

Question 1:
How we can keep our shared EA-packages in sync?

Question 2:
Our packages are under version control. If we check out a shared package (e.g. P1), it is marked as checked out in any other EA-Project. It is a fatal behaviour that we could checkin package "P1" from a EA-Project we didn`t use for editing package "P1" (see topic http://www.sparxsystems.com.au/cgi-bin/yabb/YaBB.pl?board=general;action=display;num=1168870718
).

We urgently need help....

Thanx in advance Armin

[mark.myers]

re Q2:  

Are you using the same credentials to connect to the repository or different usernames for different projects.  Not sure if this helps but a lock is placed on the repository file for the user who checked it out, therefore if P2 connects as a different user than P1 it should not be possible for P2 to check it in if P1 has it checked out. However if you use the same username to connect then you will have the situation you describe.

I am using SVN and have NOT tried this though I did notice a similar thing when I was testing checkout on the same machine (different eap file but same connection credentials)

[armin]

Hi,

as I work in two different EA-projects on the same client I'm using the same user account for connecting to version control (mks). So I don't see a workaround for this problem.

[mikewhit]

Unless you could set up a separate login username for each project ... e.g. armin.p1 and armin.p2 ... and then force explicit use of the project username each time you access the project.

Perhaps Sparx could consider adding support for project restrictions such as you mention, as a package version control setting.