Matt Doran wrote:
> Mark Phippard wrote:
>
>>I have never looked at the svnAnt code, but I imagine there is an
>>ISVNClientAdapter available for you to use in the code. It then just has
>>some really simple methods for doing stuff. You would want to look at
>>getStatus()
>>
>>Mark
>>
>>
>>
>
> I've re-implemented my ant task that fetches a summary of working copy
> status, storing the status in various ant properties. I thought I'd
> post the first cut here for review before spending much more time on
> it.....
>
> I've called the task "SummaryStatus" .... but I'm not sure it's the
> best name.... suggestions?
>
> The ant task can be called with the following syntax:
>
> <svn><summaryStatus path="wcPath" prefix="prefix."/></svn>
>
> This will set the following properties:
>
> prefix.repos.url -> the repos URL of the
> WC root
> prefix.repos.path -> the repos path
> prefix.revision.max -> the highest revision
> number in the WC
> prefix.revision.max-with-flags -> the highest revision number
> in the WC plus flags (M - modified, X - mixed)
> prefix.revision.range -> the revision range
> similar to svnversion format. e.g. 1000:1010MX
> prefix.committed.max -> the max 'last committed
> revision' (Should we even bother with these? They don't add much
> value.)
> prefix.committed.max-with-flags -> the max 'last committed
> revision' with flags
>
>
>
> I've taken the approach to specify a property prefix, so you can run
> this multiple times for different working copies in the build (if
> required). I noticed that some svnant tasks allow you to specify the
> property name to store the result, but thought that given the number
> of properties this task sets, this approach would be more
> practical..... but I'm up for suggestions.
>
> If we stick with this approach, are the property names appropriate?
>
> Is there any other info that would be useful to add?
>
> Other changes / comments:
>
> * The svnadapter patch fixes the build.properties to reference the
> correct libs..... without this the svnClientAdapter ant build fails.
> * SvnAnt was not using the latest trunk svnClientAdapter ... so I
> built a new version and used that.
> * Change SvnTask to load the JavaSVN adapter. It will be used in
> preference to the command-line client. Probably should make it
> configurable to choose your preference?? ... but this was just a
> quick fix
> * The tasks seems to work with well with both javahl and JavaSVN
> ... but the command-line adapter fails on fairly big working
> copy. I get an error "java.io.IOException: CreateProcess: svn
> info <multi-paths>". I haven't had a chance to look at it, but
> the command-line is very long (too long for windows?).
>
>
> Look forward to your feedback ...
>
>
> Regards,
> Matt
Hi there,
Any news on a review of this patch?
Cheers,
Matt
Received on Wed Aug 24 12:14:47 2005