Since Picocli does not have any dependencies on its own, it's safe to use.
It's a bit quirky to use with Scala, but it's imho the best CLI library for
java.
The only downside as Chesnay mentioned is the increased jar size. Also note
that Flink is not graal-ready.
Best,
Arvid
On Wed, Aug 12, 20
The benefit of the ParameterTool is that you do not increase your
dependency footprint by using it.
When using another CLI library you will generally package it within your
user-jar, which may or may not increase the risk of dependency conflicts.
Whether, and how large this risk is, depends na
Thank you for the clarification.
But does it offer any additional benefits that are not clearly documented?
On Tue, Aug 11, 2020 at 12:22 PM Robert Metzger wrote:
> Hi,
> there are absolutely no dangers not using ParameterTool.
> It is used by the Flink examples, and as a showcase for global
Hi,
there are absolutely no dangers not using ParameterTool.
It is used by the Flink examples, and as a showcase for global job
parameters:
https://ci.apache.org/projects/flink/flink-docs-release-1.2/monitoring/best_practices.html#register-the-parameters-globally
On Tue, Aug 11, 2020 at 7:13 PM Ma