[
https://issues.apache.org/jira/browse/SLING-11843?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17716654#comment-17716654
]
Konrad Windszus edited comment on SLING-11843 at 4/26/23 10:25 AM:
-------------------------------------------------------------------
bq. One concern that I have with Java 17 is that projects using PowerMock will
be broken - see
https://stackoverflow.com/questions/69896191/powermock-compatibility-with-jdk-17
.
I have very little hope that this will ever work with newer Java versions
(compare with discussions at
https://github.com/powermock/powermock/issues/1094), so it is probably time to
get rid of powermock in tests.
was (Author: kwin):
bq. One concern that I have with Java 17 is that projects using PowerMock will
be broken - see
https://stackoverflow.com/questions/69896191/powermock-compatibility-with-jdk-17
.
I have very little hope that this will ever work with newer Java versions, so
it is probably time to get rid of powermock in tests.
> 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)
