From 96b2469544fba40e63d009db73b41c3b07b80684 Mon Sep 17 00:00:00 2001 From: Tristan Partin Date: Wed, 26 Jan 2022 00:33:58 -0600 Subject: Rename JDK system dep to JNI JNI is a more apt name because it currently only supports the JNI. I also believe that CMake uses the terminology JNI here as well. JNI is currently the only way to interact with the JVM through native code, but there is a project called "Project Panama" which aims to be another way for native code to interact with the JVM. --- docs/markdown/snippets/jdk-renamed-to-jni.md | 6 ++++++ 1 file changed, 6 insertions(+) create mode 100644 docs/markdown/snippets/jdk-renamed-to-jni.md (limited to 'docs/markdown/snippets') diff --git a/docs/markdown/snippets/jdk-renamed-to-jni.md b/docs/markdown/snippets/jdk-renamed-to-jni.md new file mode 100644 index 0000000..d1e7f9d --- /dev/null +++ b/docs/markdown/snippets/jdk-renamed-to-jni.md @@ -0,0 +1,6 @@ +## JDK System Dependency Renamed from `jdk` to `jni` + +The JDK system dependency is useful for creating native Java modules using the +JNI. Since the purpose is to find the JNI, it has been decided that a better +name is in fact "jni". Use of `dependency('jdk')` should be replaced with +`dependency('jni')`. -- cgit v1.1