Matt,
Yeah...mine isn't as complete as yours but it was written in 2 hours,
with complete unit tests and documentation, and was really meant to fill a
void in our development team. I think our two Ant Tasks are sweet. I love
being able to use the repo information in my build for tagging build
artifacts based on the repo information. Good luck.
Take care,
Jeremy
On 11/30/05, Matt Doran <matt.doran@papercut.biz> wrote:
>
> Hi Jeremy,
>
> I still lurk around on the list. My patches were never reviewed by an
> svnant committer.... so never got included. I'm still using a custom Ant
> task that uses JavaSVN for our purposes.
>
> Your task just does an 'svn info' which doesn't tell you the status of the
> rest of the WC. My task crawled the WC looking for revision ranges and
> modified files, producing results similar to 'svnversion'. This allows you
> to easily see if you build includes any modified files. I think my
> "svnversion" ant task is also useful.
>
> Both would be worthy inclusions in svnant.
>
> Cheers,
>
> Matt Doran
> PaperCut Software Pty. Ltd.
> Phone: +61 (3) 9571 1151
> E-mail: matt.doran@papercut.biz
> Profile: http://www.papercut.biz/company.htm#matt
> Blog: http://blogs.papercutsoftware.com/matt.doran/
>
>
>
> Jeremy Whitlock wrote:
>
> Hey all,
> I see that Matt Doran had created an Ant task that implemented svn
> info so that you could apply the values from the svn info to Ant build
> properties for use later in your build file. I wrote one as well and if
> Matt never integrated his into SvnAnt, I would love to. Please get back to
> me. Also, to see how my Ant task works:
>
> http://lavender.cime.net/~jwhitlock/svninfo_ant.html<http://lavender.cime.net/%7Ejwhitlock/svninfo_ant.html>
>
> and to download/use:
>
> http://lavender.cime.net/~jwhitlock/svninfo_ant.zip<http://lavender.cime.net/%7Ejwhitlock/svninfo_ant.zip>
>
> Take care,
>
> Jeremy
>
>
Received on Thu Dec 1 09:23:01 2005