[
https://issues.apache.org/jira/browse/SLING-11843?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17716604#comment-17716604
]
Robert Munteanu commented on SLING-11843:
-----------------------------------------
[~kwin] - it would help by giving maintainers a chance to react and
incrementally fix the modules. What I am trying to prevent is having dozens of
broken builds with a lot of work to debug; e.g. Windows CI failures may be
harder to fix than failures on Java 11. And, to be honest, I don't see too many
people stepping up and fixing CI failures.
Perhaps we should be a bit more specific regarding the Java version being used
and not enable it when we know for sure it will fail. We know for a fact that
parent pom 35 is required for Java 11, so let's only enable Java 11 builds for
projects with have a recent enough parent pom version. I think we can make a
similar statement for Java 17, so I propose we conditionally enable Java 11 and
Java 17 based on the parent pom version.
> 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)
