On Thu, 28 Jun 2007, Ben Collins-Sussman wrote:
> On 6/28/07, C. Michael Pilato <firstname.lastname@example.org> wrote:
> >> I like the concept, but in addition to putting a "path" into the
> >> svn_client_conflict_description_t, I'd recommend putting an "adm_access"
> >> baton. Otherwise, won't callback implementers will be lacking a vital
> >> for working copy manipulation?
> Ah, great idea. That's a vital tool, indeed.
While implementing conflict resoultion callback bindings for JavaHL, I
ran into a bit of a snafu with regard to this key data structure:
JavaHL does not wrap libsvn_wc; it stops at libsvn_client.
I can pass the memory address of the adm_access into Java-land as a
long, but it's basically useless to everything except other JNI code
written against the Subversion bindings. Pure Java code (e.g. SVNKit)
would find this memory address to be completely useless.
Am I going to need to wrap parts of libsvn_wc for JavaHL to make
proper use of the conflict resolution callback? If so, which bits are
Received on Mon Jul 9 22:53:46 2007
- application/pgp-signature attachment: stored