[
https://issues.apache.org/jira/browse/FLINK-5378?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Lorenz Bühmann updated FLINK-5378:
----------------------------------
Description:
Is it possible to increase the Scopt version to 3.5.0? This version does also
support comma-separated lists of arguments.
I'm using this in my project and indeed I can use Maven to use the latest Scopt
version. But, once I want to deploy an uber-Jar to Flink, it obviously fails
because of two different versions of Scopt in the classpath - one in my
uber-Jar (Scopt 3.5.0) and the one shipped with Flink distribution (Scopt
3.2.0).
I know that there is another open issue regarding refactoring the CLI parser
(FLINK-1347), but as far as I can see there is no progress yet.
was:
Is it possible to increase the Scopt version to 3.5.0? This version does also
support comma-separated lists of arguments.
I'm using this in my project and indeed I can use Maven to use the latest Scopt
version. But, once I want to deploy an uber-Jar to Flink, it obviously fails
because of two different versions of Scopt in the classpath - one in my
uber-Jar (Scopt 3.5.0) and the one shipped with Flink distribution (Scopt
3.2.0).
> Update Scopt version to 3.5.0
> -----------------------------
>
> Key: FLINK-5378
> URL: https://issues.apache.org/jira/browse/FLINK-5378
> Project: Flink
> Issue Type: Wish
> Affects Versions: 1.2.0, 1.1.3, 1.3.0
> Reporter: Lorenz Bühmann
> Priority: Trivial
>
> Is it possible to increase the Scopt version to 3.5.0? This version does also
> support comma-separated lists of arguments.
> I'm using this in my project and indeed I can use Maven to use the latest
> Scopt version. But, once I want to deploy an uber-Jar to Flink, it obviously
> fails because of two different versions of Scopt in the classpath - one in my
> uber-Jar (Scopt 3.5.0) and the one shipped with Flink distribution (Scopt
> 3.2.0).
> I know that there is another open issue regarding refactoring the CLI parser
> (FLINK-1347), but as far as I can see there is no progress yet.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)