Are you aware that maven-release-plugin isn’t currently working with git submodules because of http://jira.codehaus.org/browse/SCM-530 ?
(I’m just warning you, so you wouldn’t have painful surprise one day) Wiadomość napisana przez Hervé BOUTEMY <herve.bout...@free.fr> w dniu 14 lut 2014, o godz. 09:19: > No doubt it can be done in general, but the question is on ASF (canonical) > git > repo [1] > at the moment, everything seems flat > IMHO, some git expert should work with infra to make it more structured > > Regards, > > Hervé > > [1] https://git-wip-us.apache.org/repos/asf > > Le vendredi 14 février 2014 20:23:34 Fred Cooke a écrit : >> I have my private git repo setup in a nested way. No reason you couldn't do >> that the same for this. >> >> baseurl/org/apache/mvn/core/componentA.git >> >> etc. >> >> Unsure if this addresses your concerns or not, but it's certainly neat and >> tidy at the server end, and the user can duplicate the path structure the >> same at home. >> >> Fred. >> >> On Fri, Feb 14, 2014 at 7:33 PM, Hervé BOUTEMY <herve.bout...@free.fr>wrote: >>> I'm not a git expert: if there are solutions, yes, they have to be found, >>> explained, tested, before we launch "convert everything to git" >>> >>> thank you for any good idea and then any tests from people wanting the >>> great >>> migration to happen (without wreaking havoc) >>> >>> Regards, >>> >>> Hervé >>> >>> Le vendredi 14 février 2014 17:10:07 Mark Derricutt a écrit : >>>> Jenkins could build from a super-repo that uses git submodule. >>>> >>>> Since a quite a few versions ago, git-submodules can now follow a branch >>>> rather than a fixed SHA1. >>>> >>>> So you could build/test monolithically, branch/commit individually. >>>> >>>> Compromise maybe? >>>> >>>> On 14 Feb 2014, at 6:28, Hervé BOUTEMY wrote: >>>>> each entry would mean 1 git repo + 1Jenkins job (or even more, since >>>>> plugins >>>>> have multiple Jenkins jobs: 1 for Maven 2.2.x, 1 for Maven 3.0.x, 1 >>>>> for Maven >>>>> 3.1.x) >>>>> IMHO, we're not ready for such granularity, neither at git nor Jenkins >>>>> level >>>> >>>> --------------------------------------------------------------------- >>>> To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org >>>> For additional commands, e-mail: dev-h...@maven.apache.org >>> >>> --------------------------------------------------------------------- >>> To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org >>> For additional commands, e-mail: dev-h...@maven.apache.org > > > --------------------------------------------------------------------- > To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org > For additional commands, e-mail: dev-h...@maven.apache.org >
