1
General Board / Re: Subversion Integration revisited ...
« on: May 10, 2008, 01:53:18 am »
Hi SwissSteve,
we used an easier way i think. For example we didnt give ids to each model package but rather for the whole project. I dont know whether it is the right way. And we dont have much experience in it. We just tried it out. But, it seemed to work.
Though we were a little bit disappointed about some points:
- we could not really edit the models parallel. You can work parallel when you switch to Offline and afterwards merge the xml files with an subversion client. I dont know how good this works.
- i dont see a way to update packages (in my working copy) recursively with sub-packages.
Well, here is what we did:
1. Create an empty new folder in repository using a subversion client.
2. Check out a working copy of this empty folder.
3. Start EA.
4. Create a new project in EA and save it in the working copy.
5. From the top package in the tree in EA choose 'Package Control' and 'Version Control Settings'. We gave an id for the whole project.
6. Make 'Add branch to version control' for each package in the tree. EA generates automatically folders where it keeps the xml-files.
For the *.eap file, either it was checked in automatically as we checked in the model packages or we checked it in 'manually' in a subversion client. I dont know any more. But it is in the repository and i think you need it in the repository for some not model related changes. I needed it for template packages (See the help). As i checked in the template package, it wasnt a template package in other developers working copy until i checked in the *.eap and they checked it out.
New developers had to check out the whole in an ordinary subversion client. Then start EA and open the EA-project. EA asks then to complete the version control configuration.
I hope, i could help you,
radle
we used an easier way i think. For example we didnt give ids to each model package but rather for the whole project. I dont know whether it is the right way. And we dont have much experience in it. We just tried it out. But, it seemed to work.
Though we were a little bit disappointed about some points:
- we could not really edit the models parallel. You can work parallel when you switch to Offline and afterwards merge the xml files with an subversion client. I dont know how good this works.
- i dont see a way to update packages (in my working copy) recursively with sub-packages.
Well, here is what we did:
1. Create an empty new folder in repository using a subversion client.
2. Check out a working copy of this empty folder.
3. Start EA.
4. Create a new project in EA and save it in the working copy.
5. From the top package in the tree in EA choose 'Package Control' and 'Version Control Settings'. We gave an id for the whole project.
6. Make 'Add branch to version control' for each package in the tree. EA generates automatically folders where it keeps the xml-files.
For the *.eap file, either it was checked in automatically as we checked in the model packages or we checked it in 'manually' in a subversion client. I dont know any more. But it is in the repository and i think you need it in the repository for some not model related changes. I needed it for template packages (See the help). As i checked in the template package, it wasnt a template package in other developers working copy until i checked in the *.eap and they checked it out.
New developers had to check out the whole in an ordinary subversion client. Then start EA and open the EA-project. EA asks then to complete the version control configuration.
I hope, i could help you,
radle