[
https://issues.apache.org/jira/browse/SLING-9839?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17227273#comment-17227273
]
Bertrand Delacretaz commented on SLING-9839:
--------------------------------------------
I'm not saying it is wrong but it is likely to break the build for some modules
which do not build with JDK11.
Running {{mvn -U clean verify sonar:sonar}} with JDK11 for
{{sling-org-apache-sling-adapter-annotations-it}}, for example, fails with a
{{NullPointerException}} in {{maven-failsafe-plugin}}.
That's probably easy to fix, and should be, but I didn't want to let my changes
in yesterday night before going offline and risk breaking many builds.
The best is probably to re-add my changes (or better ones) to run {{mvn
sonar:sonar}} with JDK 11, see which modules break and fix those. I just didn't
want to do that without warning others.
> Jenkins: Sonarcloud analysis with Java 11
> -----------------------------------------
>
> Key: SLING-9839
> URL: https://issues.apache.org/jira/browse/SLING-9839
> Project: Sling
> Issue Type: Improvement
> Reporter: Konrad Windszus
> Priority: Major
>
> As SonarSource is stopping support for Java 8 analysis
> (https://sonarcloud.io/documentation/appendices/move-analysis-java-11/), we
> should switch to matrix builds with Jenkins with Java 8 and 11 builds in
> parallel
> (https://www.jenkins.io/blog/2019/12/02/matrix-building-with-scripted-pipeline/
> ).
> The Java 8 build should be deployed to Apache Snapshots (for backwards
> compatibility reasons). The Java 11 build should be used for coverage
> analysis and sonar execution..
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
