I am trying to figure out how to use subversion with multi-module projects.
I will try to explain what problems I am trying to do, and the problems
I am having.
I have read several threads regarding this, but there did not seem to be
a real solution, or any news about future development to resolve the
As an example, let's say I have these modules: Module1, Module2, SharedModule.
In practice the number of modules are high, so keep that in mind.
There is a Project1, which uses Module1 and SharedModule. And there is
a Project2, which uses Module2 and SharedModule.
In case of a release I want to tag Module1 and SharedModule with "Project1-1.0"
or Module2 and SharedModule with "Project2-1.0".
I would like a layout like this:
The problem I have is how to tag modules for Project1, without tagging those
of Project2. I would have no problem to checking out the modules for Project1
seperately and thus have a working copy with only the modules for Project1
as version controlled. However then I cannot find any way to tag subdirectories.
I would have to tag Module1 and SharedModule seperately each time. That
would be fine if there were two modules, but since in my case there are about
50 it would be unworkable.
If only there was an option to do subversion actions, such as tag/branch
and merge on subdirectories in a directory that itself is not version-controlled
I would be very happy.
Since there are about 50 modules, I do not want each of them to have their
own trunk, tags and branches. This also would result in way too much work.
To unsubscribe from this discussion, e-mail: [users-unsubscribe_at_subversion.tigris.org].
Received on 2009-03-13 15:56:52 CET