Well, finding a "windows command line svn client" looks easier said than done. I've spent over an hour now trying to find a free one (I've got no use for it at the moment apart from this issue), and it's not at all clear that there is one that will do the job without messing about with 30 day trials for Syncro and the like.
I'm sure I'll find a solution, but I'd just comment that this a real nuisance, and I think either making the svn task optional or handling it via SVNKit sounds like a very good idea to me. On Jan 12, 8:08 pm, Scott Blum <[email protected]> wrote: > Just install a recent svn client, it shouldn't interfere. Freeland, we > could also consider either making the successful execution of this task > optional, or even check SVNKit into TOOLS and using that to power the Ant > task. > > On Mon, Jan 12, 2009 at 1:16 PM, gregor <[email protected]>wrote: > > > > > I'm trying to make a 1.6 build from trunk to test 1.6 and I got hit > > with this which seems to emanate from <macrodef name="gwt.getsvninfo" > > task in common.ant.xml. I use Tortoisesvn and I gather that it doesn't > > qualify as a command line svn client and this is the problem. Can I > > hack build.xml or common.ant.xml to get round this, or is there a > > recommended svn download (windows for me) that won't interfere with > > tortoise? > > > regards > > gregor --~--~---------~--~----~------------~-------~--~----~ http://groups.google.com/group/Google-Web-Toolkit-Contributors -~----------~----~----~----~------~----~------~--~---
