@@ -92,11 +92,11 @@ Contributing to the Elasticsearch codebase
92
92
93
93
** Repository:** [ https://github.com/elastic/elasticsearch ] ( https://github.com/elastic/elasticsearch )
94
94
95
- JDK 13 is required to build Elasticsearch. You must have a JDK 13 installation
95
+ JDK 14 is required to build Elasticsearch. You must have a JDK 14 installation
96
96
with the environment variable ` JAVA_HOME ` referencing the path to Java home for
97
- your JDK 13 installation. By default, tests use the same runtime as ` JAVA_HOME ` .
97
+ your JDK 14 installation. By default, tests use the same runtime as ` JAVA_HOME ` .
98
98
However, since Elasticsearch supports JDK 11, the build supports compiling with
99
- JDK 13 and testing on a JDK 11 runtime; to do this, set ` RUNTIME_JAVA_HOME `
99
+ JDK 14 and testing on a JDK 11 runtime; to do this, set ` RUNTIME_JAVA_HOME `
100
100
pointing to the Java home of a JDK 11 installation. Note that this mechanism can
101
101
be used to test against other JDKs as well, this is not only limited to JDK 11.
102
102
@@ -121,9 +121,9 @@ You can access Elasticsearch with:
121
121
122
122
### Importing the project into IntelliJ IDEA
123
123
124
- Elasticsearch builds using Java 13 . When importing into IntelliJ you will need
124
+ Elasticsearch builds using Java 14 . When importing into IntelliJ you will need
125
125
to define an appropriate SDK. The convention is that ** this SDK should be named
126
- "13 "** so that the project import will detect it automatically. For more details
126
+ "14 "** so that the project import will detect it automatically. For more details
127
127
on defining an SDK in IntelliJ please refer to [ their documentation] ( https://www.jetbrains.com/help/idea/sdk.html#define-sdk ) .
128
128
SDK definitions are global, so you can add the JDK from any project, or after
129
129
project import. Importing with a missing JDK will still work, IntelliJ will
0 commit comments