On Sat, May 23, 2009 at 9:17 AM, Stefan Sperling <stsp_at_elego.de> wrote:
> On Sat, May 23, 2009 at 09:09:22AM -0400, Mark Phippard wrote:
>> SVNKit maintains compatibility with SVN. It does not work because you
>> used a UI where they are emulating SVN, and so they recreate the SVN
>> functionality, limitations and all. They support this feature at
>> their API level so that tools that write to their API, such as
>> Subclipse and others, can use this feature.
> thanks for the explanation.
> For clarity, can you provide a pointer to the relevant subclipse
> source code that uses the API?
SVNKit has a complete API that is similar to SVN, in the sense that it
has many layers. They then provide an implementation of the JavaHL
SVNClientInterface as well, where their implementation, instead of
using JNI, implements it using their own API. Subclipse talks to
SVNKit via the JavaHL interface. So for the most part, Subclipse just
uses the JavaHL interface and we control which implementation is being
SVNKit added an extra boolean named "atomic" to the commit methods for
this feature and Subclipse just had to add some special logic to know
when SVNKit was being used so that we could call this method that was
not part of JavaHL.
The SVNKit code we use is here:
search for "atomicCommit"
Of course you'll then have to trace this into their implementation and
actual API. But that is the starting point.
Received on 2009-05-23 16:26:27 CEST