[svn.haxx.se] · SVN Dev · SVN Users · SVN Org · TSVN Dev · TSVN Users · Subclipse Dev · Subclipse Users · this month's index

RE: Incomplete xml output when using --xml to non-existent server

From: Bert Huijben <bert_at_qqmail.nl>
Date: Wed, 2 Mar 2016 19:05:21 +0100

> -----Original Message-----
> From: Johan Corveleyn [mailto:jcorvel_at_gmail.com]
> Sent: woensdag 2 maart 2016 15:05
> To: Subversion Development <dev_at_subversion.apache.org>
> Subject: Incomplete xml output when using --xml to non-existent server
>
> Hi all,
>
> A colleague of mine ran into this, and I'm wondering if it's expected
> behavior or a bug:

For me it is expected behavior. As soon as you get output on stderr and/or a non success result the xml generated by 'svn' is usually invalid. And there is no real backwards compatible way to fix this as our xml schema has no way to express errors.

It has been this way for many versions (and actually one of a few reasons I started working on SharpSvn in 2006, which eventually got me here in the project, etc.)

I would recommend switching to one of the language bindings if you really need to care for handling error conditions.
(Sometimes it is easier to work around things by just performing things recursively on an ancestor directory)

        Bert
Received on 2016-03-02 19:05:38 CET

This is an archived mail posted to the Subversion Dev mailing list.