version control questions (SVN)

[OwenInCanada]

Hi all,

May I ask a few questions on EA version control? I have a successful deployment of EA with SVN in WinXP SP3 using TortoiseSVN (TSVN) and CollabNet SVN (command line client). Although I don't use TSVN to manage EA artifacts, the EA files are in the same repo and working copy as other files that are managed by TSVN.  

1. I have the following inconsistent situation: A controlled package shows the key icon (meaning it is checked-in). The option "Package Control | Checkout..." is not available for that package. TortoiseSVN "Check For Modifications | Check repo" shows a lock (with my userid) against the xml file that corresponds to the controlled package. Because of the way we use TSVN, I have several SVN working copies of the larger (more than EA) project, and it is in one of these recent working copies that I have noticed this EA situation. I expect that I may have checked out the package (in EA) and then abandandoned that working copy; and what I am seeing is the symptom of that in a newly created working copy. Apart from losing my changes, can I just use TSVN to release or break the lock in order to restore normal behaviour in my current working copy?

2. Some of my controlled packages have the SVN-needs-lock property set and some do not. Where is that configured in EA? (I.e. in Windows, some of the TSVN icons are green check-marks and some are grey.)

3. If I add a new package as a subfolder of a package that is already version controlled, what do I have to do to put the new (sub-)package under version control. I.e., do I have to configure version control for that new package, or does it inherit from the parent?

Thank you for your advice!

Regards,

Owen

[aap]

Hi

1. Yes you can break the lock with TSVN (and lose the changes you made in your other model).

2. I think all the XMI files for your controlled packages should have svn-needs-lock set, and this is built into EA. having said that I've noticed a couple of mine don't have the property set -- a bug perhaps?

3. You have to configure the version control for the subfolder. The parent folder needs to be checked out to do this. Note that anyone else using the subpackages must sure that they have used the same Unique Ids in the project's version control settings.

Andy

[OwenInCanada]

Thanks for the advice!

[«Midnight»]

...
2. I think all the XMI files for your controlled packages should have svn-needs-lock set, and this is built into EA. having said that I've noticed a couple of mine don't have the property set -- a bug perhaps?
...

Have you brought this to Sparx' attention? They cannot address the problem if they don't know it is happening.

If you can send them a sample project, as well as all particulars (vendor, version, application edition) of every component of your VC configuration, it would help. You can attach a sample - it is always a good idea to compress the file - to the Registered Users bug report, or to an email to Sparx Support.

David