This week's book giveaway is in the OO, Patterns, UML and Refactoring forum. We're giving away four copies of Refactoring for Software Design Smells: Managing Technical Debt and have Girish Suryanarayana, Ganesh Samarthyam & Tushar Sharma on-line! See this thread for details.
We are working on a project that currently will contain 2 modules. For now, we will just call them retail and admin. We are trying to figure out a good way of setting up our repositories so that we can share common codebase betwee nthe 2 modules without it turning into a maintenance nightmare.
We thought that we might be able to use the svn:externals but that is only on a directory level basis and there will be directories that have both shared and module specific resources.
Has anyone had to do something similar that cares to share their experiences and how they approached this? I'm not sure what other information one might require to help, but if you need anything else, ask and I'll see what I can provide.
Gregg, In CVS, we would put the common code in a separate project and have the other two projects refer to it. Is there any reason you can't do that in SVN. I haven't used it much, but I can't think of any inherent reason it wouldn't work.
Originally posted by Jeanne Boyarsky: Gregg, In CVS, we would put the common code in a separate project and have the other two projects refer to it. Is there any reason you can't do that in SVN. I haven't used it much, but I can't think of any inherent reason it wouldn't work.
We are currently switching to SVN, and I can tell you: no, there is no reason to not do the same in SVN. In fact that's exactly what I would do.
The soul is dyed the color of its thoughts. Think only on those things that are in line with your principles and can bear the light of day. The content of your character is your choice. Day by day, what you do is who you become. Your integrity is your destiny - it is the light that guides your way. - Heraclitus