57adb77e6b
This helps with preventing jdk8-specific calls being checked in, because PR builders are running the compiler with the wrong settings. If the JAVA_7_HOME env variable is set, assume it points at a jdk7 and use its rt.jar when invoking javac. For zinc, just run it with jdk7, and disable it when building jdk8-specific code. A big note for sbt usage: adding the bootstrap options forces sbt to fork the compiler, and that disables incremental compilation. That means that it's really not convenient to use for normal development, but should be ok for automated builds. Tested with JAVA_HOME=jdk8 and JAVA_7_HOME=jdk7: - mvn + zinc - mvn sans zinc - sbt Verified that in all cases, jdk8-specific library calls fail to compile. Author: Marcelo Vanzin <vanzin@cloudera.com> Closes #13272 from vanzin/SPARK-15451. |
||
|---|---|---|
| .. | ||
| src/test | ||
| pom.xml | ||
| README.md | ||
Java 8 Test Suites
These tests require having Java 8 installed and are isolated from the main Spark build. If Java 8 is not your system's default Java version, you will need to point Spark's build to your Java location. The set-up depends a bit on the build system:
-
Sbt users can either set JAVA_HOME to the location of a Java 8 JDK or explicitly pass
-java-hometo the sbt launch script. If a Java 8 JDK is detected sbt will automatically include the Java 8 test project.`$ JAVA_HOME=/opt/jdk1.8.0/ build/sbt clean java8-tests/test
-
For Maven users,
Maven users can also refer to their Java 8 directory using JAVA_HOME.
$ JAVA_HOME=/opt/jdk1.8.0/ mvn clean install -DskipTests$ JAVA_HOME=/opt/jdk1.8.0/ mvn -pl :java8-tests_2.11 testNote that the above command can only be run from project root directory since this module depends on core and the test-jars of core and streaming. This means an install step is required to make the test dependencies visible to the Java 8 sub-project.