minifuture

A stripped to the bones CompletableFuture backport for Java 6+ and Android (API level 14+).

This is a minimized (105 KiB) version of the streamsupport-cfuture component without any dependencies that provides only CompletableFuture and the API necessary to use it and nothing else (no Streams, no ForkJoinPool and such). It is intended for projects that only have a need for a CompletableFuture backport and want minimal dependency footprint. The public API surface comprises the following interfaces / classes:

• java8.util.concurrent.CompletableFuture
• java8.util.concurrent.CompletionException
• java8.util.concurrent.CompletionStage
• java8.util.function.BiConsumer
• java8.util.function.BiFunction
• java8.util.function.Consumer
• java8.util.function.Function
• java8.util.function.Supplier

The CompletableFuture API is the one from Java 12, i.e. it contains the Java 9 (JEP 266) enhancements and the exception handling methods introduced in Java 12 (JDK-8211010). The project can be compiled with Java 6 and should be compatible with any OpenJDK based JVM and Android versions starting from API level 14.

build.gradle:

dependencies {
    implementation 'net.sourceforge.streamsupport:streamsupport-minifuture:1.7.4'
}

Maven:

<dependency>
    <groupId>net.sourceforge.streamsupport</groupId>
    <artifactId>streamsupport-minifuture</artifactId>
    <version>1.7.4</version>
</dependency>

LICENSE

GNU General Public License, version 2, with the Classpath Exception (and CC0 1.0 for JSR-166 derived code)

License clarification

• This library's latest-version includes 18 *.java files.
• 9 of said files are under CC0 1.0 License

  Where said license allows you to use almost any sub-license you want.

• 9 other of said files are under GPL with Classpath license-exception.

Where said "Classpath" license-exception allows your executables:

• "to link this library" (no matter if statically or dynamically),
• "and to copy and distribute the resulting executable under terms of your choice",
• But those who re-distribute this library's source-code form, not "executable" binary, can only do that under the terms of GPL 2.0.

  In other words, some of our source-codes always remain GPL 2.0, but your executable can link to them statically and/or dynamically, which is far more permissive than LGPL and/or GPL.