Skip to content

Commit 5de7b3c

Browse files
(ninja) Update doc related to java version (#246)
Co-authored-by: Antonio Murgia <antonio.murgia@agilelab.it>
1 parent 0a102ef commit 5de7b3c

File tree

2 files changed

+5
-5
lines changed

2 files changed

+5
-5
lines changed

CONTRIBUTING.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -31,7 +31,7 @@ skip these steps and jump straight to submitting a pull request.
3131

3232
# IDE setup
3333

34-
To get started with Whitefox development, you need JDK 11 installed. Since the project is managed with Gradle, any
34+
To get started with Whitefox development, you need JDK 17 installed. Since the project is managed with Gradle, any
3535
IDE that works with Gradle v8.3 will be a good fit. We internally use IntelliJ IDEA Community Edition.
3636

3737
# Protocol

docsite/docs/development_guidelines.md

Lines changed: 4 additions & 4 deletions
Original file line numberDiff line numberDiff line change
@@ -4,7 +4,7 @@
44

55
To get started you need:
66

7-
- JDK 11 installed
7+
- JDK 17 installed
88

99
alternatively a recent IntelliJ IDEA Community Edition version is enough.
1010

@@ -16,13 +16,13 @@ Gradle I kindly suggest to start from [its awesome docs](https://gradle.org/guid
1616
The server is [quarkus](https://quarkus.io) application that exposes a REST API implementing Whitefox and
1717
delta-sharing protocol. If you never worked with Quarkus, have a look at [its awesome doc](https://quarkus.io/get-started/).
1818

19-
The app is developed and run for JVM 11 because hadoop libraries (which are a dependency of delta-lake kernel) do
20-
not run properly on newer versions of the JVM.
19+
The app is developed and run for JVM 17, even if hadoop libraries (which are a dependency of delta-lake kernel) are
20+
not certified to run on JDK > 11 we are not encountering any issue so far.
2121

2222
As soon as you clone the project you should verify that you are able to build and test locally, to do so you need to
2323
run the `check` command of Gradle, you can achieve that using either `gradlew` script in the project root (`.
2424
/gradlew check`) or run the same [gradle task from intellij](https://www.jetbrains.com/help/idea/work-with-gradle-tasks.html).
25-
If you're default jvm is not version 11, you can run `gradlew` passing another java home as follows:
25+
If you're default jvm is not version 17, you can run `gradlew` passing another java home as follows:
2626
`./gradlew -Dorg.gradle.java.home=<PATH_TO_JAVA_HOME> build`.
2727

2828
Sometimes IntelliJ will tell you have build errors, especially when moving from one branch to the other. The problem

0 commit comments

Comments
 (0)