See also the issue: Analyzing Java8 code with JDK11 - deprecations which we face when we tried migration to JDK11 for analyzing
Gradle needs to be upgraded to 5.0 to support java11. We are using lombok as an annotation processor for all our projects and older versions of lombok is broken for java11. If lombok is upgraded to newer version then lot of code files need to be changed.
lombok changelog : https://projectlombok.org/changelog
gradle support: https://adtmag.com/blogs/watersworks/2018/11/gradle-5-0.aspx
Thanks for your answer. In my case I had to skip those tasks:
./gradlew -Dorg.gradle.java.home=/Library/Java/JavaVirtualMachines/jdk-11.0.7.jdk/Contents/Home module:sonarqube \ -x kaptDevDebugKotlin \ -x compileDevDebugJavaWithJavac \ -x kaptDevDebugAndroidTestKotlin \ -x compileDevDebugAndroidTestKotlin \ -x compileDevDebugAndroidTestJavaWithJavac \ -x compileDevDebugUnitTestKotlin \ -x compileDevDebugUnitTestJavaWithJavac
It would be nice to have a better way to set up it.
I moved this Scanner for Gradle topic to another one (to not mix with the previous one).
Do you still have questions around that ? Otherwise i’ll close it.
Hi @mickaelcaro, I had no questions related to SonarScanner for Gradle Maybe it was a tricky place to split the original discussion.