[svnbook commit] r3559 - * src/en/book/ch08-embedding-svn.xml
codesite-noreply at google.com
codesite-noreply at google.com
Thu Jul 16 09:03:25 CDT 2009
Author: stsp at elego.de
Date: Thu Jul 16 07:02:52 2009
New Revision: 3559
Modified:
trunk/src/en/book/ch08-embedding-svn.xml
Log:
* src/en/book/ch08-embedding-svn.xml
(svn.developer.usingapi.otherlangs): SVNKit has been open source
for some time. Update the comparison between SVNKit and JavaHL
to reflect this fact.
Modified: trunk/src/en/book/ch08-embedding-svn.xml
==============================================================================
--- trunk/src/en/book/ch08-embedding-svn.xml (original)
+++ trunk/src/en/book/ch08-embedding-svn.xml Thu Jul 16 07:02:52 2009
@@ -966,14 +966,19 @@
confuse SVNKit with javahl, and easier still to not even
realize which of these libraries you are using, folks should
be aware that SVNKit differs from javahl in some significant
- ways. First, SVNKit is not developed as open source
- software and seems to have at any given time only a few
- developers working on it. Also, SVNKit's license is more
- restrictive than that of Subversion. Finally, by aiming to
- be a pure Java Subversion library, SVNKit is limited in
- which portions of Subversion can be reasonably cloned while
- still keeping up with Subversion's releases. This has
- already happened once—SVNKit cannot access BDB-backed
+ ways. First, while SVNKit is developed as open source
+ software just like Subversion, SVNKit's license is more
+ restrictive than that of Subversion.
+ <footnote><para>Redistributions in any form must be accompanied
by
+ information on how to obtain complete source code for the
+ software that uses SVNKit and any accompanying software that
+ uses the software that uses SVNKit.
+ <ulink url="http://svnkit.com/license.html" /></para>
+ </footnote>
+ Finally, by aiming to be a pure Java Subversion library, SVNKit
+ is limited in which portions of Subversion can be reasonably
+ cloned while still keeping up with Subversion's releases.
+ This has already happened once—SVNKit cannot access
BDB-backed
Subversion repositories via the <literal>file://</literal>
protocol because there's no pure Java implementation of
Berkeley DB that is file-format-compatible with the native
More information about the svnbook-dev
mailing list