Build

Run the build.

Run the benchmarks.

Clean all jar files, classes, and generated documentation.

Compile all classes.

Run the JaCoco code coverage.

Create the documentation from the documentation sources. API Javadocs are created as well.

Download all required jar files. Actually those are only compile time dependencies. The database can be used without any dependencies.

Create the h2.zip file and the Windows installer.

Create the regular h2.jar file.

Create the file h2android.jar. This only contains the embedded database, plus the H2 Android API. Debug information is disabled.

Create the h2client.jar. This only contains the remote JDBC implementation.

Create the file h2jaqu.jar. This only contains the JaQu (Java Query) implementation. All other jar files do not include JaQu.

Create the file h2mvstore.jar. This only contains the MVStore.

Create the file h2small.jar. This only contains the embedded database. Debug information is disabled.

Create the Javadocs of the API (incl. the JDBC API) and tools.

Create the Javadocs of the implementation.

This will build a release of the H2 .jar files and upload it to file:///data/h2database/m2-repo. This is only required when a new H2 version is made.

This will build a 'snapshot' H2 .jar file and upload it to the local Maven 2 repository.

Build the jar file without downloading any files over the network. If the required files are missing, they are are listed, and the jar file is not built.

Just run the spellchecker.

Switch the source code to the current JDK.

Compile and run all tests. This does not include the compile step.

Test the local network of this machine.

Print the system properties.

Compile and run all fast tests. This does not include the compile step.

This build target is used for the automated build. It copies the result of the automated build (including test results, newsfeed, code coverage) to the public web site.

Build the h2console.war file.