[
https://issues.apache.org/jira/browse/SLING-11843?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17722140#comment-17722140
]
Stefan Seifert commented on SLING-11843:
----------------------------------------
according to the log the build failed for
* sling-org-apache-sling-testing-osgi-mock
* sling-org-apache-sling-testing-sling-mock
* sling-org-apache-sling-contentparser-testutils
by they compile nicely with java 11 on my machine. some of them fail with java
17, though.
lof of the others that failed look like modules not touched for a longer time,
so likely they use a too old sling-parent.
i still would propose to switch the defaults to make this failures easily
visible, but of course should discuss this on the list first.
> 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)
