Sparx Systems Forum

Enterprise Architect => General Board => Topic started by: K N on February 22, 2013, 06:18:22 am

Title: Subversion and EA repository
Post by: K N on February 22, 2013, 06:18:22 am

Hi

I have a MySQL repository integrated with EA and using SlikSVN for the version control.

I had a project A (for example) in the repository and had assigned package control (a1.xml) to one of the packages in the project.

Then, for some reason, i made a project transfer (for example Project B) to the DBMS and the old data (project A) gets wiped off from the DBMS. I never changed/deleted the associated version control file.

Is it possible that i can sync Project B with the latest version of project A i.e. a1.xml?
because when i try applying package control in project B pointing to the same a1.xml file it gives me a warning that "file already exists".

Let me know if you have any questions or anything is not clear

Thanks
KN

Title: Re: Subversion and EA repository
Post by: Helmut Ortmann on February 22, 2013, 07:54:05 am

Hi,

I hope I got the right picture.

You are using project p1 with controlled packages (svn or so) with DBMS or *.eap.

You can reuse arbitrary controlled packages in other projects. To do this just import the package for the first time of usage in your additional project (this also imports the settings of the controlled package).

Synchronisation is done by:
- Get Latest
- Get All Latest
- Checkout / Checkin

I would use EA release >= 9 because of handling of cross package references.

In Resources you find further information.

By the way: This is a good solution for slow WAN connections.

By the way: In the forum you find also valuable tips of the past.

By the way: With SVN Branches you are also able to work with different release of a package in different projects.

Controlled packages are a powerful concept most people catch only after some time and some not always funny experiences (so was my way).

Kind regards,

Helmut

Title: Re: Subversion and EA repository
Post by: Geert Bellekens on February 22, 2013, 06:53:13 pm

Yes you can.

First you need to create the version control settings in project B, pointing to the working folder where your a1.xml is stored.
Then you right click on a package and select Package Control|Get package... Select your new version control setting, and select the file a1.xml.
Now you can once again check-out, edit, check-in your package.

Geert