Apache Derby 10.15.2.0 Release
Use the links below to download a distribution of Apache Derby. You should always verify the integrity of distribution files downloaded from a mirror.
There are four different distributions:
- bin distribution - contains the documentation, javadoc, and jar files for Derby.
- lib distribution - contains only the jar files for Derby.
- lib-debug distribution - contains jar files for Derby with source line numbers.
- src distribution - contains the Derby source tree at the point which the binaries were built.
Release Notes for Apache Derby 10.15.2.0
These notes describe the difference between Apache Derby release 10.15.2.0 and the preceding release 10.15.1.3.
If you are upgrading from a 10.14 release or earlier, then you should read the 10.15.1.3 release notes. Those release notes describe changes which you will need to make to your classpath.
The most up to date information about Derby releases can be found on the Derby download page.
Apache Derby is a pure Java relational database engine using standard SQL and JDBC as its APIs. More information about Derby can be found on the Apache web site. Derby functionality includes:
- Embedded engine with JDBC drivers
- Network Server
- Network client JDBC drivers
- Command line tools: ij (SQL scripting), dblook (schema dump) and sysinfo (system info)
The 10.15 release family supports the following Java and JDBC versions:
- Java SE 9 and higher with JDBC 4.2.
This is a maintenance (bugfix) release. No new features were added.
The following issues are addressed by Derby release 10.15.2.0. These issues are not addressed in the preceding 10.15.1.3 release.
|DERBY-7038||Upgrade ant version and re-write javadoc build targets to use improved <javadoc>task|
|DERBY-7040||Add dependency stanzas to maven poms|
|DERBY-7041||null pointer exception when creating view based on other views|
|DERBY-7046||NoClassDefFoundError on java -jar derbynet.jar|
|DERBY-7050||In build.xml of derby root there's a vestigial target|
|DERBY-7052||Reordering and (mildly) reorganizing build.xml Ant targets around buildsource|
|DERBY-7053||Further top build.xml streamlining|
|DERBY-7057||Unreferenced failing target in main build|
No issues required detailed release notes.
Derby release 10.15.2.0 was built using the following environment:
- Branch - Source code came from the 10.15 branch.
- Machine - Mac OSX 10.11.6.
- Ant - Apache Ant(TM) version 1.10.2 compiled on February 3 2018.
- Compiler - All classes were compiled by the javac from OpenJDK 64-Bit Server VM 18.9 (build 11+28, mixed mode).
It is essential that you verify the integrity of the downloaded files using the PGP and SHA-512 signatures. SHA-512 verification ensures the file was not corrupted during the download process. PGP verification ensures that the file came from a certain person.
The PGP signatures can be verified using PGP or GPG. First download the Apache Derby KEYS as well as the asc signature file for the particular distribution. It is important that you get these files from the ultimate trusted source - the main ASF distribution site, rather than from a mirror. Then verify the signatures using ...
% pgpk -a KEYS % pgpv db-derby-X.Y.tar.gz.asc or % pgp -ka KEYS % pgp db-derby-X.Y.tar.gz.asc or % gpg --import KEYS % gpg --verify db-derby-X.Y.tar.gz.asc
To verify the SHA-512 checksums on the files, you need to use a platform-specific program. On Mac OSX, this program is called shasum, on Linux it is called sha512sum, and on Windows it is called CertUtil.
We strongly recommend that you verify your downloads with both PGP and SHA-512.