Messages

1

General Board / Re: Howto work with Version Control branches

« on: July 10, 2008, 10:49:59 pm »

Hello Howard,
thank you for the in detail explanation.
I gave it a try but did not succeed.
After step 10 I end up with an Model where all subtrees are empty. In the branch directory where I had set a sticky tag for the branch, all files are replaced with those from the main trunk.

I'm using EA 7.1 Build 831 with CVS as Version Control system.

Do you have any additional suggestions?

Thanks, Harald

p.s.: I'm aware that it is not possible to merge the XMI files. We planned to store older revisons as baseline within EA too, and make a compare / merge within EA if this would be necesarry.

2

General Board / Re: Howto work with Version Control branches

« on: July 10, 2008, 12:53:41 am »

Sorry, I did not mean the Version of the Properties page for the package but the version of the release. Normally I set a baseline / version within the version control system.
I simply need to open a branch within the VC for a package with an older revision and would like to edit this "old" revision.

3

General Board / Howto work with Version Control branches

« on: July 10, 2008, 12:19:57 am »

Hello,
I read through all the version control documentation and searched the forum, but I could find nothing concerning branches within Version Control.

Our scenario:
We have business analysts working on the requirements model. To hand it over to the development, they check it in (V1.0) and start working on the requirements for the next release (V1.1).
During development some problems have been found in the requirements model and need to be corrected. Here normally a Version Control branch would be opened for V1.0.
Unfortunatelly I found no way in EA to checkout an older version for editing. I always end up with the latest version from the repository.
I tried to workaround this by checking out using EA, retrieving a sticky version using my VC client and importing this XMI. But then my package got locked again by EA.
Is there an offical way managing branches, or any hint for a workaround.
Thanks in advance.
H.

4

General Board / Re: Problem with "feature" full qualified tagged v

« on: August 14, 2008, 09:24:49 pm »

Hi,
build 832 is out and the release notes mention this problem to be fixed.

I've just given it a short try and it seems to work.
All tagged values will be replaced by their fully qualified names, but the data remains intact.
The only weird thing I've found: If you are using tagged value associations within your profile, you will only get a drill down to select the referenced element, if the tagged value options are set to display only short names. Otherwise the data displayed is a GUID and no drilldown is present.

Harald

5

General Board / Howto work with Baselines in Version Control

« on: July 10, 2008, 12:48:08 am »

Hello,
we have several business domains within our model, each managed in its own package. Each business domain is handled by an own business analyst. The packages are under Version Control, but each with its own intervall for check-in.
If all fits together a release is prepared, marking all this current checked in exports with a baseline (revision) within the version control.
For the next release some (or all) of the packages might be amended and checked in again with different intervalls.
The development team needs all the packages for this release.
What I would like to do is to perform an "Get latest for revision/baseline", so a developer does not need to get each package manually by using
Package Control -> File History -> select specific version -> Retrieve
and hopefully uses the correct version all the time.

Any sugestions?
Thanks in advance.
H.