diff --git a/README.md b/README.md
index cd8aa9aa..0616ebe8 100644
--- a/README.md
+++ b/README.md
@@ -29,7 +29,7 @@ and LeJOS with the rich local navigation stack and the remote support in the fut
 
 The library has support for `Debian Jessie` & `Debian Stretch`. 
 In this release, we have finished the support for `Debian Stretch` for EV3 and you could
- use OpenJDK 11 or OpenJDK 12 EA and it is amazing! 
+ use OpenJDK 11, or OpenJDK 14 and it is amazing! 
 
 If you need to use any Raspberry Pi Boards, I recommend to use the stable `EV3Dev` 
 [Debian Jessie](http://www.ev3dev.org/downloads/) release.
@@ -57,7 +57,7 @@ The project has been designed with the following solution in mind:
 |---|------------------|--------------------------------------------|-------------------------|
 | 1 | Platforms        | BrickPi BrickPi3 PiStorms              | EV3                     |
 | 2 | OS               | Debian Jessie                              | Debian Jessie/Stretch          |
-| 3 | JVM              | OpenJDK 11                               | OpenJDK JRI 11 / 12 ea          |
+| 3 | JVM              | OpenJDK 14                               | OpenJDK JRI 11 / 12 / 13 / 14           |
 | 4 | EV3Dev Kernel    | 4.4.47-19-ev3dev-rpi2 | 4.14.71-ev3dev-2.3.0-ev3 |
 | 5 | ev3dev-lang-java | 0.7.0                                      | 2.4.12                   |
 
diff --git a/docs/adr/README.md b/docs/adr/README.md
index b4d47fbb..83ab983f 100644
--- a/docs/adr/README.md
+++ b/docs/adr/README.md
@@ -8,7 +8,6 @@ in this project.
 * [New Display API](adr-display-api.md)
 * [Changes to leJOS sensor API](adr-lejos-sensor.md)
 * [Support for newer Java versions](adr-openjdk-builds.md)
-* [Gradle-plugin integration](adr-plugin-integration.md)
 
 ## References:
 
diff --git a/docs/adr/adr-plugin-integration.md b/docs/adr/adr-plugin-integration.md
deleted file mode 100644
index c64ddc8c..00000000
--- a/docs/adr/adr-plugin-integration.md
+++ /dev/null
@@ -1,36 +0,0 @@
-# Gradle-plugin integration (Dec 2019)
-
-This ADR is about the ev3dev-lang-java's gradle plugin:
-https://github.com/ev3dev-lang-java/gradle-plugin
-
-## Dependency uploading
-
-This plugin provides functionality for uploading the program's JAR dependencies
-to the on-brick library directory. The purpose of this is to make first-time
-setup easier while still using standard JARs (i.e. non-fat jar that does
-not contain it's dependencies inside).
-
-To achieve this, the Gradle plugin integrates with the dependency
-system present in Gradle. It does not have an effect on dependency
-resolution. Rather, it is a consumer of the runtimeClasspath API provided
-by Gradle's Java plugin that collects the JAR dependencies that are
-needed at runtime. The libraries that are returned by Gradle are
-then uploaded from the local Maven repository to the brick.
-
-For this reason, it is necessary to use [`implementation`][impl] or [`api`][api]
-dependency configuration in `build.gradle` for runtime libraries.
-While using `compileOnly` would not break the plugin, but it would
-prevent it from seeing these dependencies (and their transitive
-dependencies) and uploading them.
-
-Lombok is an exception here, because its classes are not used at runtime,
-they are used only during `javac` compilation for annotation processing.
-It can therefore be included using just `compileOnly`
-
-Now one has to choose between `api` and `implementation`.
-For this, take a look at a take of `java-library` authors on this [here][api_vs_impl].
-
-
-[impl]: https://docs.gradle.org/current/userguide/java_plugin.html#tab:configurations
-[api]: https://docs.gradle.org/current/userguide/java_library_plugin.html#sec:java_library_separation
-[api_vs_impl]: https://docs.gradle.org/current/userguide/java_library_plugin.html#sec:java_library_recognizing_dependencies