[
https://issues.apache.org/jira/browse/SLING-11843?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17716652#comment-17716652
]
Konrad Windszus commented on SLING-11843:
-----------------------------------------
For me the ultimate goal of this issue to ease and foster contributions.
Building should work with Java 11/17 because that is what developers naturally
expect these days (and what they have setup on their machines). Also the
majority of potential contributors is working with Windows machines I guess, so
if tests fail for them they probably won't contribute.
What this means for the maintainers is secondary here, because each maintainer
can decide to not support certain versions/OS (for whatever reason) by just
deviating from the default in the {{sling-module.json}}.
The broken CI builds will also give some transparency with regards to whether
it is supposed to work at all with 11/17 and Windows. Currently a contributor
won't know whether a failing local build/test case is an issue with her/his
setup or an issue due to the lack of support of this module.
> 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
>
> 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)
