flink-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "ASF GitHub Bot (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (FLINK-3077) Add "version" command to CliFrontend for showing the version of the installation
Date Wed, 09 Dec 2015 10:59:11 GMT

    [ https://issues.apache.org/jira/browse/FLINK-3077?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15048482#comment-15048482

ASF GitHub Bot commented on FLINK-3077:

Github user mxm commented on the pull request:

    >Also, what is the procedure for creating a release artifact locally[without GPG keys,
Apache id, etc.] so I can check that this works okay for those too?
    The release scripts do nothing fancy. Essentially, they just set the release version and
delete the .git folder. You can do the same locally. The GPG keys and Apache id is just for
actual deployment of the build artifacts.

> Add "version" command to CliFrontend for showing the version of the installation
> --------------------------------------------------------------------------------
>                 Key: FLINK-3077
>                 URL: https://issues.apache.org/jira/browse/FLINK-3077
>             Project: Flink
>          Issue Type: Improvement
>          Components: Command-line client
>            Reporter: Robert Metzger
>            Assignee: Sachin Goel
>             Fix For: 1.0.0
> I have the bin directory of Flink in my $PATH variable, so I can just do "flink run"
on the command line for executing stuff.
> However, I have multiple Flink versions locally and its hard to find out which installation
the bash is picking in the end.
> adding a simple "version" command will resolve that issue and I consider it helpful in

This message was sent by Atlassian JIRA

View raw message