| commit | c4b6a660e65a5461058129d0d19b40e78edfcc6d | [log] [tgz] |
|---|---|---|
| author | Lee Rhodes <leerho@users.noreply.github.com> | Thu Jul 22 15:09:06 2021 -0700 |
| committer | Lee Rhodes <leerho@users.noreply.github.com> | Thu Jul 22 15:09:06 2021 -0700 |
| tree | f335e8912f988edf0c02db8d4778b726e6d6a325 | |
| parent | 5555a433f92f74243f93d58043fc0e221b38706e [diff] |
Add .clover/ to gitignore and to rat excludes
=================
The goal of this component of the library is to provide high performance access to native memory for primitives and primitive arrays. It also provides consistent views into heap-based primitive arrays, Java ByteBuffers and memory mapped files. This package is general purpose, has minimal external runtime dependencies and can be used in any application that needs to manage data structures outside the Java heap.
Please visit the main DataSketches website for more information.
If you are interested in making contributions to this site please see our Community page for how to contact us.
Datasketches memory currently supports Java 8 up to and including Java 13.
In order to use the library in Java 9 and above, you must provide the following runtime arguments to the JVM:
--add-opens java.base/java.nio=org.apache.datasketches.memory \ --add-opens java.base/jdk.internal.misc=org.apache.datasketches.memory \ --add-opens java.base/jdk.internal.ref=org.apache.datasketches.memory
For example, to run your local application with full compatibility for the Java module system, you might use the following command:
$JAVA \ --module-path mods \ --add-opens java.base/java.nio=org.apache.datasketches.memory \ --add-opens java.base/jdk.internal.misc=org.apache.datasketches.memory \ --add-opens java.base/jdk.internal.ref=org.apache.datasketches.memory \ --module my.main.application.module
where mods is your module path and my.main.application.module is your own JPMS module:
module datasketches.memory.multirelease.test { requires org.apache.datasketches.memory; }
NOTE: This component accesses resource files for testing. As a result, the directory elements of the full absolute path of the target installation directory must qualify as Java identifiers. In other words, the directory elements must not have any space characters (or non-Java identifier characters) in any of the path elements. This is required by the Oracle Java Specification in order to ensure location-independent access to resources: See Oracle Location-Independent Access to Resources
IMPORTANT: This project is structured as a maven multi-module project. Building this project might affect plugins that require early dependency resolution, such as the javadoc and eclipse plugins. The build instructions below have been modified to use the process-classes phase (instead of compile) for these use cases. For more information, see this Maven Reactor issue.
This DataSketches component is pure Java and requires the following JDKs to compile:
This DataSketches component is structured as a Maven project and Maven is the recommended Build Tool.
There are two types of tests: normal unit tests and tests run by the strict profile.
To run normal unit tests:
$ mvn clean test
To run the strict profile tests:
$ mvn clean test -P strict
To run javadoc on this multi-module project, use:
$ mvn clean process-classes javadoc:javadoc -DskipTests=true
To run the eclipse plugin on this multi-module project, use:
$ mvn clean process-classes eclipse:eclipse -DskipTests=true
To install jars built from the downloaded source:
$ mvn clean install -DskipTests=true
This will create the following Jars:
This project makes use of Maven toolchains to ensure that the correct Java compiler version is used when compiling source files. Ensure that your local environment has been configured according to the toolchain documentation.
There are no run-time dependencies.
See the pom.xml file for test dependencies.
For more information on the project configuration, the following topics are discussed in more detail:
In order to build and contribute to this project, please read the relevant IDE documentation: