[
https://issues.apache.org/jira/browse/FLINK-33543?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Matthias Pohl resolved FLINK-33543.
-----------------------------------
Fix Version/s: 1.19.0
Assignee: Matthias Pohl
Resolution: Fixed
master:
[a1aed4f877099328d4833f8a2781d2edbaaddc70|https://github.com/apache/flink/commit/a1aed4f877099328d4833f8a2781d2edbaaddc70]
> Move Java 17-specific code into its own module to please Intellij
> -----------------------------------------------------------------
>
> Key: FLINK-33543
> URL: https://issues.apache.org/jira/browse/FLINK-33543
> Project: Flink
> Issue Type: Improvement
> Components: API / Type Serialization System, Build System
> Affects Versions: 1.19.0
> Reporter: Matthias Pohl
> Assignee: Matthias Pohl
> Priority: Major
> Labels: pull-request-available
> Fix For: 1.19.0
>
>
> FLINK-32380 introduced support for Java records (which are introduced in Java
> 14). Test classes were added and included via Maven profiles. This works on
> the command line. Intellij runs into issues though when build {{flink-core}}.
> [~snuyanzin] filed
> [IDEA-338060|https://youtrack.jetbrains.com/issue/IDEA-338060/How-to-make-IntellijIdea-aware-of-maven-compiler-plugin-testExcludes]
> to cover this issue.
> A workaround on the Flink side is to have a dedicated module for Java 17 code
> (more specifically the test classes which use Java record). This would make
> {{flink-core}} compilable again. The newly introduced module can be enabled
> for the {{java17}} profile.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
