If you have a version controlled package in project A and import it to project B, it will be the same package. It means if you do some changes in A, check the package in, then check it out in B, it will reflect your last made changes to this package.
If you have more versions of package A. E.g.
- version 12
- version 13 (stable)
- version 14
- version 15
and you want to update package A in project B to version 13, it's not possible using the EA versioning capabilities itself.
You have to make a branch/tag of the SVN folder with your EA xmi files. Make a different working copy of your SVN repository directed to this branch. Update it manually to version 13 (using SVN instructions). Then configure Version control settings for your package in project B with this different Working copy. And finally check out (or get latest) this package by EA in project B.
If you make changes to this package in project B and check them in (by EA), they will go to the branch, not to the trunk of your SVN repository. (Although I think you don't want to make changes to your package in Project B.)
If you will have a next major version of your package in project A and want to have it also in project B, just merge the XMI file in the branch with the desired version from trunk. (SVN uses a diff procedure when merging so instead of simple merging it is better to clear the xmi file in the branch, save, check in and only after that run the merge.)
I'm not a SVN guru, maybe it could be achieved in more simpler way.
I'm not actively using this process, I've tested only parts of it. But I think it should work.
