I was about to enter an INFRA JIRA for the migration. see below the suggested text. Let me know your thoughts. ——————————————————————————————————————— Migration of the Ant project and subprojects to Git
vote : http://ant.1045680.n5.nabble.com/VOTE-migration-to-git-tt5715081.html#none vote-result : http://ant.1045680.n5.nabble.com/migration-to-git-intermediate-summary-tc5715104.html#none here are the GIT Modules that we need to create ant : http://svn.apache.org/repos/asf/ant/core/ ivy : http://svn.apache.org/repos/asf/ant/ivy/core/ ivyde : http://svn.apache.org/repos/asf/ant/ivy/ivyde/ easyant-buildtypes : http://svn.apache.org/repos/asf/ant/easyant/buildtypes/ easyant-core : http://svn.apache.org/repos/asf/ant/easyant/core/ easyant-easyant4e : http://svn.apache.org/repos/asf/ant/easyant/easyant4e/ easyant-plugins : http://svn.apache.org/repos/asf/ant/easyant/plugins/ easyant-skeletons : http://svn.apache.org/repos/asf/ant/easyant/skeletons/ easyant-tasks : http://svn.apache.org/repos/asf/ant/easyant/tasks/ antlibs-antunit : http://svn.apache.org/repos/asf/ant/antlibs/antunit/ antlibs-common : http://svn.apache.org/repos/asf/ant/antlibs/common/ antlibs-compress : http://svn.apache.org/repos/asf/ant/antlibs/compress/ antlibs-dotnet : http://svn.apache.org/repos/asf/ant/antlibs/dotnet/ antlibs-props : http://svn.apache.org/repos/asf/ant/antlibs/props/ antlibs-svn : http://svn.apache.org/repos/asf/ant/antlibs/svn/ antlibs-vss : http://svn.apache.org/repos/asf/ant/antlibs/vss/ ——————————————————————————————————————— Regards, Antoine On May 13, 2014, at 9:17 AM, Matt Sicker <boa...@gmail.com> wrote: > On Tuesday, 13 May 2014, Antoine Levy Lambert <anto...@gmx.de> wrote: > >> Hello Matt, >> >> this is interesting - thanks for pointing this out since I am a newbie in >> git land. >> >> does one need to do some advance planning to make a module become a >> submodule of >> another repository aggregating the submodules ? >> >> Nope! You use it somewhat like svn:external, but you manually keep the > commit ID in sync to whatever you want. I find it useful to use a tag for > that commit. Otherwise you end up with a history like "update submodule" > over and over again. > > >> there would be a use case for an aggregation of the complete ant family, >> maybe for an aggregation of the antlibs too … >> >> If there's a master build.xml or similar that can just iterate through all > the projects and build them in order, that's a neat use case. > > > -- > Matt Sicker <boa...@gmail.com> --------------------------------------------------------------------- To unsubscribe, e-mail: dev-unsubscr...@ant.apache.org For additional commands, e-mail: dev-h...@ant.apache.org
