+1 for switching to git.
Although there may be one slight build issue for Nick when dealing with the external
modules (e.g. pi4soa, savara, etc). Currently the svn based hudson jobs check out a
jbosstools build structure and then the project module to be built - in separate
sub-folders. The build structure contains some publish scripts.
Although the git part of the hudson job configuration allows multiple repositories to be
specified, it only defines a 'Local subdirectory for repo (optional)' attribute
for the git section as a whole, not per repository.
So currently it attempts to fetch all of the git repositories into the same location in
the workspace - which does not seem to work.
----- Original Message -----
We got our svn mirror now but after working with it a bit its
basically just as slow as normal svn (if you can get it to work).
...thus i'm wondering if anyone can come up with good reasons to *not*
just move all new development over to git and simply kill off
the SVN completely for our jbosstools trunk development ?
3.2.x would stay in SVN.