[
https://issues.apache.org/jira/browse/SLING-11843?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17717502#comment-17717502
]
Robert Munteanu commented on SLING-11843:
-----------------------------------------
Later edit: I ran the full Java 11 build with
{{JAVA_HOME=/usr/lib64/jvm/java-11 mvn clean install clean --fail-at-end | tee
java11-install-build.log}} ( clean/install/clean to keep the disk usage sane ).
I've attached it as [^java11-install-build.log] .
After the full build, I see 90 failures and 240 successful builds. I think a
25% failure rate is too high to 'just' enable it. To be sure I didn't miss
anything, I will run the full build with Java 8 as well. But I think twe should
at least give a heads-up on dev@sling to allow maintainaners to fix builds in
advance, should they desire to do so.
> Change Default JDK/OS for Jenkins Builds to JDK11/17 on Unix/Windows
> --------------------------------------------------------------------
>
> Key: SLING-11843
> URL: https://issues.apache.org/jira/browse/SLING-11843
> Project: Sling
> Issue Type: Improvement
> Components: CI
> Reporter: Konrad Windszus
> Assignee: Konrad Windszus
> Priority: Major
> Attachments: java11-install-build.log
>
>
> Currently our Jenkins jobs by default only run on JDK8 with Linux.
> I would propose to change the default (mentioned in
> https://cwiki.apache.org/confluence/display/SLING/Sling+module+descriptor#Slingmoduledescriptor-DefaultValues)
> to
> * Build with JDK 11 and 17 on
> * Windows and Linux
> Although this might break some builds, I think it is time now to make all
> modules compatible with it once we touch it for whatever reason.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
