Consider the following questions:
How do you handle project dependencies with
Our project is made up of multiple inter-dependent repositories. Currently we manage those with
svn:externals. What's the best way to handle those with
How do you split a very big repository in smaller components using
These are some of our most frequently asked questions.
The topic appears to be a big pain point for many software teams adopting
git, so in this article I'll try to shed some light on the issue.
Obviously project dependencies and build infrastructure are two intertwined areas, and even internally at Atlassian a discussion sparked on the "Future of Builds".
Having separate repositories as opposed to having a single one can make some things harder. But it's a relatively natural – sometimes mandatory – step in the evolution of a software project for at least two major reasons: increasing build times, and shared dependencies between projects.