Upgrading to maven-scm 1.1 will fix other issues (CONTINUUM-1521 currently some users can't use continuum if they use StarTeam !).
IMHO we don't have here a high pressure to release something ASAP this can wait end of august. -- Olivier 2008/8/11 Wendy Smoak <[EMAIL PROTECTED]>: > I don't want to be in a situation where we can't release because we > depend on snapshots of other things. Git support would be nice, but > IMO it isn't vital for 1.2 -- it can go in 1.2.1 or 1.2.2, whenever > the scm release happens. Can it go on a branch for now? > > There's probably a reasonable workaround for the Appearance thing > (edit the xml file directly?) but I imagine you'll have it fixed soon > enough. > > There is plenty of other work on trunk that is finished and ready to > go. I'm looking at staging 1.2 in the next week or two unless someone > else would like to do the honors. > > -- > Wendy > > On Sun, Aug 10, 2008 at 3:21 PM, Olivier Lamy <[EMAIL PROTECTED]> wrote: >> Hi, >> Yes we can. >> But we are dependant on scm release (which is dependant on maven >> parent pom release too :-) ). >> FYI, I have tested git provider an it works fine. (if you want to test >> I have created two repos [1] in git-hub for testing purpose) >> The only limitation is the support of project with modules (CONTINUUM-1843). >> By the way, I'd like to fix CONTINUUM-1831 which IMHO is blocker for a >> release. >> >> -- >> Olivier >> [1] http://github.com/olamy/scm-git-test-one-module.git/ and >> http://github.com/olamy/scm-git-test.git/ >
