Apache Derby 10.15.1.3 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.
You are currently using http://mirror.reverse.net/pub/apache/. If you encounter a problem with this mirror, then please select another. If all mirrors are failing, there are backup mirrors at the end of the list. See status of mirrors.
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.1.3
These notes describe the difference between Apache Derby release 10.15.1.3 and the preceding release 10.14.2.0.
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 feature release. The following new feature was added:
- JPMS modularization - Derby has been re-packaged as a set of JPMS modules. This introduced a new jar file, derbyshared.jar, required by all configurations. Module diagrams for Derby configurations can be found in the javadoc for the 10.15 public API.
Existing users who want to continue running Derby with a classpath should read the extended release note for issue DERBY-6945 (see below).
Existing users who want to run Derby with a module path should consult the module diagrams in the javadoc for the 10.15 public API. Templates for wiring together a module path can be found in the setEmbeddedCP, setNetworkServerCP, and setNetworkClientCP scripts located in the bin directory of the release distributions, as described by the "Manually setting the CLASSPATH/MODULEPATH environment variables" topic in the Getting Started With Derby guide.
The following issues are addressed by Derby release 10.15.1.3. These issues are not addressed in the preceding 10.14.2.0 release.
|DERBY-7020||Fix release targets to account for modularization changes|
|DERBY-7018||Test the demo programs after the changes made by DERBY-6945|
|DERBY-7016||Adjust the set*CP scripts to include derbyshared.jar and to set a MODULEPATH variable as well|
|DERBY-6981||"SQLSTATE: XJ001, SQLERRMC: java.lang.NullPointerException XJ001.U"|
|DERBY-6980||Documentation changes to accompany jigsaw-modularization of derby|
|DERBY-6973||Provide SHA-512 checksums on future releases|
|DERBY-6945||Re-package Derby as a collection of jigsaw modules|
|DERBY-6856||Make it possible to build Derby using JDK 9|
|DERBY-5543||include debug info in derby builds uploaded to maven|
Compared with the previous release (10.14.2.0), Derby release 10.15.1.3 introduces the following new features and incompatibilities. These merit your special attention.
Summary of Change
Modularize Derby, cleanly partitioning its packages across a small set of JPMS components.
Symptoms Seen by Applications Affected by Change
A new jar file (derbyshared.jar) has been added. All Derby configurations require it. In addition, the derbytools.jar library is now required when running the network server and/or when using Derby DataSources.
Slightly different privileges must be granted to the Derby jar files when running under a Security Manager.
Derby jar files can now be wired into a module path for use by module-aware applications.
Incompatibilities with Previous Release
Legacy applications may fail if their classpaths don't contain the required jar files. Code common to all Derby configurations has been isolated in the new derbyshared.jar file. DataSources have moved from derbyclient.jar and derby.jar into derbytools.jar
Legacy applications which run under a Java SecurityManager may fail due to insufficient privilege grants.
Rationale for Change
Derby was divided into JPMS components for the following reasons:
- Footprint - Modularization reduces Derby's footprint when running embedded on resource-constrained devices.
- Security - Modularization lets Derby protect its code via package-level encapsulation.
Application Changes Required
Consult the module diagrams for configurations described on the landing page of the 10.15 public API. Then adjust your application's classpath as follows:
- Remote client - When running remote client applications, make sure that the classpath includes derbyshared.jar. Remote applications which use Derby DataSources should also include derbytools.jar.
- Embedded engine - When running the embedded engine, make sure that the classpath includes derbyshared.jar. Embedded applications which use Derby DataSources should also include derbytools.jar.
- Network server - When running the network server, make sure that the classpath includes derbyshared.jar and derbytools.jar. This is not necessary if you boot the server via the java -jar derbyrun.jar pattern. derbyrun.jar sets up its own classpath correctly.
- Tools - When running Derby tools like ij, dblook, and sysinfo, make sure that the classpath includes derbyshared.jar. Again, no change should be necessary if you boot the tools via the java -jar derbyrun.jar pattern.
Java security policy files must grant slightly different privileges to Derby jar files. This is because packages have moved to different ProtectionDomains (chiefly into derbyshared.jar) and because an additional privilege is needed in order to read the module path. For more information, see the Configuring Java Security topic in the Derby Security Guide and consult the following template policy files in the demo/templates directory of the bin distribution:
- clientTemplate.policy - Privileges needed by remote client applications.
- engineTemplate.policy - Privileges needed by applications which embed the Derby engine.
- serverTemplate.policy - Privileges needed when running the network server.
- toolsTemplate.policy - Privileges needed when running Derby tools.
Derby release 10.15.1.3 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.