Hey all, is anyone here using maven multi-module projects and git? We're looking to move from subversion to git but seem to be arguing back and forth over how best to actually handle it:
a) a git repository per module b) one huge repository for every module ( what we have with svn ) c) several git repositories with several modules grouped by type ( infrastructure, domain, user interface ) One of the current problems with mavens git integration is that it does a 'git push' upon release, which would push all commits to the upstream repository regardless of weather you wanting to do so at that point in time. Whilst annoying, this may be a problem we have to just 'deal with' ( this has been fixed in SNAPSHOTs of the git scm plugin so won't be a problem eventually ). One of the main problems I see is that git tags cover the entire repository, so if one needed to branch two modules and work on them concurrently, you'd need to separate clones of the entire repository which could start to get confusing. Wheras is each module was its own repository, you could just branch and checkout each repo in place. I was wondering what other people on the posse have done in this situation? I guess it's only limited to git but also mercurial or other dvcs's that tag on the entire repo rather than a path like svn. Mark -- Pull me down under... -- You received this message because you are subscribed to the Google Groups "The Java Posse" group. To post to this group, send email to [email protected]. To unsubscribe from this group, send email to [email protected]. For more options, visit this group at http://groups.google.com/group/javaposse?hl=en.
