L.S., Finished moving things around in SVN and raised https://issues.apache.org/jira/browse/INFRA-3730 to get the git repository re-initialized. The CI build at https://builds.apache.org/job/ServiceMix-Plugins/ has been updated with the new configuration as well.
Regards, Gert Vanthienen ------------------------ FuseSource Web: http://fusesource.com Blog: http://gertvanthienen.blogspot.com/ On Tue, Jun 21, 2011 at 8:13 AM, Jean-Baptiste Onofré <[email protected]> wrote: > Hi Willem, > > FYI, it's already possible (I do it ;)), for instance: > > git svn init --prefix=origin/ --trunk=trunk --branches=branches --tags=tags > https://svn.apache.org/repos/asf/servicemix/components > git svn fetch --log-window-size=10000 > > Regards > JB > > On 06/21/2011 03:21 AM, Willem Jiang wrote: >> >> +1, >> It could be great if we can use git svn to manage the codes on the svn >> repository. >> >> On 6/20/11 8:20 PM, Gert Vanthienen wrote: >>> >>> L.S., >>> >>> >>> The only part of ServiceMix that's not yet available using git (via >>> http://git.apache.org/) are our maven plugins (i.e. the repository >>> exists but nothing ever got mirrored over to that repository). Before >>> I ping infra@ to have a look at it, I would like to propose to alter >>> the SVN layout for those projects. >>> >>> We currently have separate trunk/branches/tags for every plugin (e.g. >>> >>> http://svn.apache.org/repos/asf/servicemix/maven-plugins/jbi-maven-plugin/) >>> >>> with some svn:externals definitions to allow checking all the plugins >>> from the maven-plugins-pom project. If we slightly modify this layout >>> to resemble that of the bundles project (with a single >>> trunk/tags/branches for all the bundles), we would have a layout >>> that's a lot more convenient to work with once you use git-svn and >>> which still works fine with svn and Maven's release plugin. >>> >>> >>> Wdyt? >>> >>> Gert Vanthienen >>> ------------------------ >>> FuseSource >>> Web: http://fusesource.com >>> Blog: http://gertvanthienen.blogspot.com/ >>> >> >> >
