Matthias Pohl created FLINK-33342:
-------------------------------------
Summary: JDK 17 CI run doesn't set java17-target profile
Key: FLINK-33342
URL: https://issues.apache.org/jira/browse/FLINK-33342
Project: Flink
Issue Type: Bug
Components: Build System / Azure Pipelines, Build System / CI
Reporter: Matthias Pohl
In contrast to the jdk11 CI run which has the java11-target profile set (see
[tools/azure-pipelines/build-apache-repo.yml:138|https://github.com/apache/flink/blob/9b63099964b36ad9d78649bb6f5b39473e0031bd/tools/azure-pipelines/build-apache-repo.yml#L138]),
it's missing for the jdk17 CI run (see
[tools/azure-pipelines/build-apache-repo.yml:149|https://github.com/apache/flink/blob/9b63099964b36ad9d78649bb6f5b39473e0031bd/tools/azure-pipelines/build-apache-repo.yml#L149]).
The profile for the source version (i.e. {{java11}} and {{java17}}) are
automatically activated through the JDK version of the run.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
