[gwt-contrib] Re: C:\GWT_source\common.ant.xml:209: cannot launch command svn info

2009-01-18 Thread Alex Epshteyn
How exactly does the svninfo task contribute to the build? I'm still getting a gwt-windows-0.0.0 directory as output. Would be nice to have a revision number there instead. On Jan 12, 11:00 pm, Freeland Abbott gwt.team.fabb...@gmail.com wrote: I've actually never had trouble getting a

[gwt-contrib] Re: C:\GWT_source\common.ant.xml:209: cannot launch command svn info

2009-01-18 Thread Alex Epshteyn
I see that the rev number is inserted into About.properties. It would be nice if this also appeared in the output directory name. Having gwt.version = 0.0.0 isn't very useful. It's a bit annoying to look for the rev number and manually rename the directory after every build. On Jan 18,

[gwt-contrib] Re: C:\GWT_source\common.ant.xml:209: cannot launch command svn info

2009-01-18 Thread Freeland Abbott
There's a difference between the release number (e.g. 1.5.3 for a release, or 0.0.0 for an arbitrary desk build) and the SVN revision of the sources (which might, accounting for branches and mutation, be something like 1...@4327:4364M). The SVN version is burned into About.properties, About.txt,

[gwt-contrib] Re: C:\GWT_source\common.ant.xml:209: cannot launch command svn info

2009-01-13 Thread Eric Ayers
FWIW, I use the cygwin version of svn on windows. Works just like Unix! Of course, Tortoise is a great graphical client for Windows. On Tue, Jan 13, 2009 at 9:03 AM, gregor greg.power...@googlemail.comwrote: Yes, that's what I eventually did. I chose the CollabNet svn command line client

[gwt-contrib] Re: C:\GWT_source\common.ant.xml:209: cannot launch command svn info

2009-01-13 Thread Scott Blum
Freeland, I believe there is a Java SVN frontend that will gracefully degrade through: 1) Your installed svn libraries through JNI 2) Command line svn 3) SvnKit Would that make this option less repulsive? On Mon, Jan 12, 2009 at 11:00 PM, Freeland Abbott gwt.team.fabb...@gmail.com wrote: I've

[gwt-contrib] Re: C:\GWT_source\common.ant.xml:209: cannot launch command svn info

2009-01-13 Thread Freeland Abbott
Repulsive is a strong word, but yes, I like it better as more able to avoid mismatches in an otherwise functional development environment. But they'd still be possible, so would we eventually be having the same discussion anyway? (In particular, I think knorton has said he edits common.xml to

[gwt-contrib] Re: C:\GWT_source\common.ant.xml:209: cannot launch command svn info

2009-01-13 Thread steve
Use the tigris (apache 2.0 / apache 2.2) binaries - they don't actually require (or contain) apache ... http://subversion.tigris.org/servlets/ProjectDocumentList?folderID=91 Get the zip (last download link on the page) and add the bin folder to your path. S

[gwt-contrib] Re: C:\GWT_source\common.ant.xml:209: cannot launch command svn info

2009-01-12 Thread Scott Blum
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

[gwt-contrib] Re: C:\GWT_source\common.ant.xml:209: cannot launch command svn info

2009-01-12 Thread gregor
FYI - it appears I'm not alone in this http://svn.haxx.se/users/archive-2008-10/0491.shtml On Jan 13, 12:11 am, gregor greg.power...@googlemail.com wrote: 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

[gwt-contrib] Re: C:\GWT_source\common.ant.xml:209: cannot launch command svn info

2009-01-12 Thread Ian Petersen
On Tue, Jan 13, 2009 at 4:10 PM, gregor greg.power...@googlemail.com wrote: 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

[gwt-contrib] Re: C:\GWT_source\common.ant.xml:209: cannot launch command svn info

2009-01-12 Thread Freeland Abbott
I've actually never had trouble getting a command-line client, but that's beside the point. We can make no svn and also not compatible messages be non-blocking errors, though as I mentioned that raises the question of whether anything should be blocking... and if not, whether we're getting