just take as example that you like to checkout all maven core plugins in one go because you like to do some refactoring/checks/upgrade. That would require you to go into each plugin project and get the stuff from there. And where would you put the aggregator pom for CI and development builds?
Same applies to all other projects which are kind of 'aggregator' like maven-core, shared, etc LieGrue, strub ----- Original Message ----- > From: Benson Margulies <bimargul...@gmail.com> > To: Maven Developers List <dev@maven.apache.org>; Mark Struberg > <strub...@yahoo.de> > Cc: > Sent: Tuesday, September 4, 2012 11:18 PM > Subject: Re: Git as the canonical SCM > > Mark, I disagree. Any group of modules that is released together can > just have a git repo. What case do you have in mind where we'd need to > fight with the git submodule madness? > > For others: if a project wants to move to git, the project must > provide a <del>sacrificial victim</del> volunteer to help with git > infrastructure. > --------------------------------------------------------------------- To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org For additional commands, e-mail: dev-h...@maven.apache.org
