1. Features

2. Command line client

3. Competition

4. Licensing

5. History

6. Adoption

7. External links

SVNKit is an open-source, pure Java software library for working with the Subversion version control system. It is free to use on opensource projects but requires that you buy a commercial license to use to develop with proprietary software. It implements virtually all Subversion features and provides API to work with Subversion working copies, access and manipulate Subversion repositories.

Features

Major SVNKit features are:

• Repository access over http(s)://, svn(+ssh):// and file:// protocols.
• Support for all working copy operations.
• Repository administration: create, load, dump and replay operations.
• Low-level API that allows to interact with Subversion repository directly on Subversion protocol level.
• Complete JavaHL API implementation.
• SVNKit is known to work on Windows, Mac OS X, Linux, BSD, SunOS, OS/2 and OpenVMS.
• SVNKit is JDK 1.5 compatible.

Features available in the native Subversion client, but missing in SVNKit:

• Local access (file://) to Berkeley DB based repositories (SVNKit only provides local access to default FSFS type of repositories).
• Experimental "Serf" HTTP access (SVNKit only provides support for DAV access).
• Some of HTTP authentication methods (e.g. SSPI) are not fully supported by the latest version of SVNKit.

Command line client

Part of SVNKit library is a command line Subversion client implemented on top of SVNKit. It is compatible with the native Subversion command line client and may be used in environments where it is not possible to install native Subversion or from within applications (e.g. Apache Ant scripts) that could not rely on the native Subversion presence.

Competition

JavaHL is a JNI wrapper of the native Subversion C code. JavaHL could be used instead of SVNKit in most of the use cases.

However, SVNKit implements JavaHL API and thus both SVNKit and Subversion JNI wrapper could be used simultaneously to let user choose what suits his environment better. A fair comparison of SVNKit and JavaHL can be found in Subversion Book. Both SVNKit and JavaHL have their own advantages and disadvantages.

Licensing

SVNKit implements a dual licensing scheme. By default SVNKit is licensed under a licensing terms similar to those of GPL, that means, in general, that there are no restrictions or limitations on SVNKit usage as long as it is being used in an open-source project.

For closed-source projects, a commercial license has to be purchased.

History

In 2005, a software company called TMate Software Ltd. announced the 1.0.0 release of JavaSVN — a pure Java Subversion client library. Since then, the project has been renamed to SVNKit.

Versions of SVNKit prior to 0.9.3 were licensed under BSD license terms, later licensing scheme has been changed to dual licensing.

Adoption

SVNKit is known to be used in:

• SmartSVN Subversion GUI client by the company WANdisco.
• IntelliJ IDEA IDE by the company JetBrains.
• TeamCity Continuous Integration Server by the company JetBrains.
• Subclipse - Eclipse Subversion plugin.
• Subversive Team Provider for Eclipse - another Eclipse Subversion plugin.
• JIRA bug tracking system by the company Atlassian.
• FishEye revision control browser by the company Atlassian.
• JDeveloper by Oracle.
• and many other products...

External links

• [https://svnkit.com/ SVNKit home web site]
• Subversion home web site
• Subversion book

• Baba Mast Nath
• Baba Mazari
• Baba Medan Konya
• Baba Mensah
• Baba Meydan-e Olya
• Baba Mohammed ben-Osman
• Baba Mohan Rama
• Baba Mountain (Macedonia)
• Baba Muhammad Dzukogi
• Baba Mukteshwar Puri, Kosli
• Baba Mungipa College of Law
• Babamunida brucei
• Babamunida callista
• Babamunida debrae
• Babamunida hystrix
• Babamunida javieri
• Babamunida kanaloa
• Babamunida plexaura
• Baba Nanak
• Baba Nanak Shrine in Baghdad
• Baba Nand Singh ji
• Ba. (band)
• Baban Daware
• Baban (disambiguation)
• Babando