@@ -80,8 +80,9 @@ This does require the use of the relatively recent [JEP-454: Foreign Function &
8080This is the primary way we envision calling Swift code from server-side Java libraries and applications.
8181
8282Required language/runtime versions:
83- - ** Swift 6.1** , because of dependence on rich swift interface files
84- - ** JDK 25+** , the most recent LTS release which includes the stable Foreign Function and Memory APIs.
83+ - ** Swift 6.1** , because of dependence on rich swift interface files
84+ - ** JDK 25+**
85+ - We are validating the implementation using the currently supported non-LTE release, which at present means JDK-25.
8586
8687## swift-java jextract --mode=jni
8788
@@ -101,7 +102,7 @@ This project contains multiple builds, living side by side together.
101102
102103You will need to have:
103104- Swift (6.1.x+)
104- - Java (24 + for FFM, even though we support lower JDK targets)
105+ - Java (25 + for FFM, even though we support lower JDK targets)
105106- Gradle (installed by "Gradle wrapper" automatically when you run gradle through ` ./gradlew ` )
106107
107108### Preparing your environment
@@ -120,12 +121,12 @@ however any recent enough Java distribution should work correctly. You can use s
120121# Install sdkman from: https://sdkman.io
121122curl -s " https://get.sdkman.io" | bash
122123sdk install java 17.0.15-amzn
123- sdk install java 24 .0.1-amzn
124+ sdk install java 25 .0.1-amzn
124125
125- sdk use java 24 .0.1-amzn
126+ sdk use java 25 .0.1-amzn
126127```
127128
128- The use of JDK 24 is required to build the project, even though the libraries being published may target lower Java versions.
129+ The use of JDK 25 is required to build the project, even though the libraries being published may target lower Java versions.
129130
130131❗️ Please make sure to ` export JAVA_HOME ` such that swift-java can find the necessary java libraries!
131132When using sdkman the easiest way to export JAVA_HOME is to export the "current" used JDK's home, like this:
0 commit comments