Apache Derby: Source Code
This page provides information for developers on how to check out and build the Derby source code. The official Derby releases are available on the Downloads page.
Derby source code
Derby source is stored in the Subversion (SVN) repository at Apache. For Derby web site source, see the Apache Derby Web Site page. The rest of this section describes where to get the Derby source code.
First, download and install Subversion from http://subversion.apache.org/
Currently Derby has the following branches:
Use the command shown below to check out the source code for a branch:
svn co https://svn.apache.org/repos/asf/db/derby/code/branches/branch/
Where branch is the number of the branch. For example, the following command checks out the source code for the 10.14 branch:
svn co https://svn.apache.org/repos/asf/db/derby/code/branches/10.14/
Use the command shown below to check out the development trunk:
svn checkout https://svn.apache.org/repos/asf/db/derby/code/trunk/
Production use of Derby should use official Derby releases or snapshot builds off the branches (or self built jars off the branches with bug fixes).
The development trunk (http://svn.apache.org/repos/asf/db/derby/code/trunk) is a development code line, which supports:
- Development of new features.
- Early access to new features for testing.
The development trunk is not suitable for production use because:
- It contains new features that have only undergone limited testing and that may corrupt data and/or return incorrect results.
- It may create on-disk database formats that are not upgradable to future releases of Derby. Databases created by official Derby releases will be upgradable to future versions.
How to build Derby
Instructions for building Derby are in a file named BUILDING.html at the root of the source code tree.
How to test Derby
Instructions for testing Derby are in the source code tree in java/testing/README.htm.
The previous link points to java/testing/README.htm in the development trunk. If you want to access the instructions in a specific branch, access the file directly by checking out the branch or the development trunk.
Also, see the tests page for test results resources.
How to submit a patch
Last updated: September 18, 2017