You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@flink.apache.org by "Matthias Pohl (Jira)" <ji...@apache.org> on 2023/11/14 12:17:00 UTC
[jira] [Created] (FLINK-33543) Move Java 17-specific code into its own module to please Intellij
Matthias Pohl created FLINK-33543:
-------------------------------------
Summary: 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
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)