Sounds like git submodules [1] may be appropriate here. There's a lot of bad press on submodules [2], so one needs to be sure they are the right thing for the job, but in this case they may be ideal as they allow each submodule to be updated independently of the parent project, so that a parent repo admin needs to decide when to update the master parent to a new version of a submodule.
Alternately, git subtrees are another option that accomplish a similar goal. [3] I've been managing several interrelated projects and stayed away from submodules because of the bad rap, but in hind sight, they are exactly the right thing for certain project relationships. If the goal is to have separate repos for each submodule, but also be able to select specific versions of each submodule for inclusion in a parent project, they are a viable option. [1] http://git-scm.com/book/en/v2/Git-Tools-Submodules & https://medium.com/@porteneuve/mastering-git-submodules-34c65e940407 [2] https://codingkilledthecat.wordpress.com/2012/04/28/why-your-company-shouldnt-use-git-submodules/ [3] http://blogs.atlassian.com/2013/05/alternatives-to-git-submodule-git-subtree/ -Bruce From: "Bertrand Delacretaz (JIRA)" <[email protected]<mailto:[email protected]>> Reply-To: "[email protected]<mailto:[email protected]>" <[email protected]<mailto:[email protected]>> Date: Thursday, April 2, 2015 at 12:21 AM To: "[email protected]<mailto:[email protected]>" <[email protected]<mailto:[email protected]>> Subject: [jira] [Commented] (SLING-3987) move from Subversion to Git [ https://issues.apache.org/jira/browse/SLING-3987?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14392285#comment-14392285 ] Bertrand Delacretaz commented on SLING-3987: -------------------------------------------- I agree about one Git repo per module, but there must be a simple way to run a full build + integration tests from a master pom. And also as Carsten says a simple way to checkout and pull all modules. move from Subversion to Git --------------------------- Key: SLING-3987 URL: https://issues.apache.org/jira/browse/SLING-3987 Project: Sling Issue Type: Task Components: Best practices Reporter: Oliver Lietz track work for moving to Git [Wiki: Move from Subversion to Git|https://cwiki.apache.org/confluence/display/SLING/Move+from+Subversion+to+Git] [discussion @dev|http://apache-sling.73963.n3.nabble.com/jira-Created-SLING-3987-move-from-Subversion-to-Git-td4040882.html#a4040901] with [~cziegeler], [~bdelacretaz], [~fmeschbe], [~justinedelson], [~rombert] and [~radu.cotescu] -- This message was sent by Atlassian JIRA (v6.3.4#6332)
