[
https://issues.apache.org/jira/browse/FLINK-33301?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17776611#comment-17776611
]
Matthias Pohl commented on FLINK-33301:
---------------------------------------
Isn't this only required when building the artifacts? The corresponding checks
will be executed right at the start (as long as {[-Prelease}}) is specified.
That would make the release manager aware of the fact that he/she has to use
{{./mvnw}} and the specific Java version. Changing the Java version would fix
the issue and the release manager could proceed. WDYT?
> Add Java and Maven version checks in the bash script of Flink release process
> -----------------------------------------------------------------------------
>
> Key: FLINK-33301
> URL: https://issues.apache.org/jira/browse/FLINK-33301
> Project: Flink
> Issue Type: Bug
> Components: Release System
> Affects Versions: 1.18.0
> Reporter: Jing Ge
> Assignee: Jing Ge
> Priority: Minor
> Fix For: 1.19.0
>
>
> During the release, Flink requires specific version of Java and Maven[1]. It
> makes sense to check those versions at the very beginning of some bash
> scripts to let it fail fast and therefore improve the efficiency.
>
> [1][https://lists.apache.org/thread/fbdl2w6wjmwk55y94ml91bpnhmh4rnm0|https://lists.apache.org/thread/fbdl2w6wjmwk55y94ml91bpnhmh4rnm0]
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
