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

Re: Pure java subversion library

From: Garrett Rooney <rooneg_at_electricjellyfish.net>
Date: 2004-10-04 17:00:36 CEST

Alexander Kitaev wrote:
> Hello Garrett,
>>Interesting. How far along is it at this point? I see an
>>awful lot of code, how much of it is functional? Does the
> There are two parts in the library: low level and high level.
> Low level part is more or less finished and provides the same functionality
> as declared in subversion/include/svn_ra.h, i.e. it allows one to perform
> all read and write operations on repository without creating and managing
> working copy files. Svn, http, and https protocols are supported, however
> https is limited by the java cryptographic support, I didn't investigate it
> a lot, but with some sites ssl connection works fine and with some it
> doesn't work.
> High level part provides an API similar to the javahl bindings and its
> default implementation works with the same working copy files format as
> "native" svn library. Not all the methods are implemented but there are
> already commit,update,import,export,copy,move and property management
> methods (all methods work with the wc files). Merge and status are not
> implemented yet. My milestone is to provide a command line java client that
> will work using this library and will implement all the features (or all
> useful features) of the "native" client. This way I will be able to
> bootstrap the library and make sure that it works in the reallife
> conditions.


> There are unit tests and they all pass at the moment, so all the declared
> API is functional at least to the level defined in the unit tests :)

Have you tried testing on a system other than windows yet? I'm seeing a
whole lot of test failures (at least for the part of the tests I can
run, I don't have apache set up on this machine, so I'm just testing the
svnserve part). One possible cause is that there seems to be an EOL
difference between stuff checked out by the svn command line tool and
stuff checked out by your library. For example, the README.txt files
you write out are ending up with dos line endings, but the ones svn
writes out are native unix line endings.

> I hope eventually all this information along with the javadoc will appear on
> the website.


>>eclipse plugin do anything useful at this point?
> There are two plugins. One just wraps the library and another is a simple
> eclipse view that allows one to browse repository, view files and their
> props, similar to the web svn browser with some more information provided.
> It was tested with eclipse 3.1. To test the "browser" plugin download
> 01.10.2004 version, because latests version doesn't contain it, only the
> wrapper plugin. This eclipse view plugin has very little practical meaning
> and was written merely as a test app for the "low level" functionality of
> the library.

Cool, I'll have to play around with it. I'm mostly interested in this
just for the purposes of an eclipse plugin that doesn't require native
code. This looks like a promising start.


To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org
Received on Mon Oct 4 17:01:04 2004

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

This site is subject to the Apache Privacy Policy and the Apache Public Forum Archive Policy.