tysonjh commented on pull request #12366: URL: https://github.com/apache/beam/pull/12366#issuecomment-665175699
> Ah, yes. To run the same commands as the Java11 builds you must set some properties. For example on mac: > > ``` > git checkout github/pr/12366 # I have fetch spec set up like this > > ./gradlew \ > -PcompileAndRunTestsWithJava11 \ > -Pjava11home=/Library/Java/JavaVirtualMachines/jdk-11-latest/Contents/Home \ > :sdks:java:extensions:sql:datacatalog:compileTestJava > ``` > > I actually got a different failure: https://gradle.com/s/gegzdydsbu2si > > ``` > Execution failed for task ':sdks:java:extensions:sql:datacatalog:compileTestJava'. > > release version 11 not supported > ``` > > That seems a bit odd. I think I did not reproduce the problem properly or there are differences between my JDK11 and the one on Jenkins. > > CC @tysonjh as we talked the other day about whether it mattered to make these unique Gradle targets versus just configuring these properties in the Jenkins job. When I run with Java 11 I use the following (example from different task): ./gradlew clean ./gradlew -Dorg.gradle.java.home=/usr/local/buildtools/java/jdk11 :runners:direct-java:validatesRunner --scan ---------------------------------------------------------------- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. For queries about this service, please contact Infrastructure at: us...@infra.apache.org
