Thanks for the help, @NicoB. For the immediate term, I have continued using Java 8 for our analysis build. Certainly for the short term, this will be sufficient as we’re not using any Java 10 language features that would require a java 10 compiler.

I’ll see if I can get any information from the plugin maintainer and, should it be fixed, hope this is the only issue.

I’ll see if I can find a roadmap for when Java 10 will be supported. For me, the priority is less around the version of Java used on the server-side and more about the environments performing the analysis. Probably, for this specific issue, it’s really when Java 9 will be supported. But it will be useful for our team when we need to make decisions around changing major versions if we have a better understanding of the roadmaps for our various tools.

I’ll see if I can find a roadmap for when Java 10 will be supported. For me, the priority is less around the version of Java used on the server-side and more about the environments performing the analysis.

Makes sense. What I can tell is that here @ SonarSource the teams are looking into the nitty-gritty details of what it would take to support those latest versions of Java (some of the JDK changes are substantial), and also determine a strategy that makes sense on the long run (given the evolving Java lifecycle). No firm update at this stage, but a clearer plan should take shape over the next couple of months.

That too makes sense. We’ve just done our own upgrade, which wasn’t too bad in the scheme of things but was more labor-intensive that previous Java releases. So I can empathize with the process there. As you stated, because the updates will be more frequent, having that strategy will be important. I’ll keep checking back when I remember

So, just as an update, the Sonargraph integration plugin doesn’t support Java 9/10 and won’t until SonarQube does. I hope we’re not getting into chicken/egg territory. Hopefully, there will be something soon(ish) around support for this