[
https://issues.apache.org/jira/browse/FLINK-33301?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17779150#comment-17779150
]
Jing Ge commented on FLINK-33301:
---------------------------------
The value(my intention) is to fail faster before maven is called, like I
mentioned the entry point is script not maven. IMHO, anything we built to
improve the efficiency will need to be maintained. That is the cost. The key
point is how often the built thing will be used vs. how often it need to be
maintained. Afaik, the versions of Java or maven might need to be
changed/maintained once every 2 years or even longer.
But, I got your point. Your thoughts are rational too. Let's stay with your
solution and we could still come back after we got more feeling/feedback about
it. 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, 1.19.0
> Reporter: Jing Ge
> Assignee: Jing Ge
> Priority: Minor
> Labels: pull-request-available
>
> 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)
