【问题标题】:Using Picocli, how do I require a positional argument and then optional arguments depending on the value of the positional argument使用 Picocli,我如何需要一个位置参数,然后是可选参数,具体取决于位置参数的值
【发布时间】:2020-02-27 07:29:44
【问题描述】:

我有一种情况,我需要三个强制参数(field1field2field3。然后我希望用户输入一个 command name(强制,值可以是 create、@ 987654326@等)。命令名必须输入,并且必须是单数(只能输入其中一个)。

有些命令会有参数,有些则没有。我该如何处理?

我尝试了以下方法,但出现错误:

ArgGroup has no options or positional parameters, and no subgroups
public class CliParserArgs {
    @Option(names = {"--field1"}, required = true)
    private String field1;

    @Option(names = {"--field2"}, required = true)
    String field2;

    @Option(names={"--field3"}, required = true)
    String field3;

    @Option(names = {"-h", "--help"}, usageHelp = true) boolean help;

    class Create {
        private final String val;
        public Create(final String val) {
            this.val = val;
        }
    }

    class ListObjects {
        private final String val;
        public ListObjects(final String val) {
            this.val = val;
        }
    }

    @ArgGroup(heading = "Command", exclusive = true, multiplicity = "1")
    Create create;
    ListObjects listObjects;

    public static void main(String[] args) {
        CliParserArgs cliParserArgs = new CliParserArgs();
        CommandLine cmd = new CommandLine(cliParserArgs);
        CommandLine.ParseResult parseResult = cmd.parseArgs(args);
        System.err.println("parse results: " + parseResult.matchedArgs().toString());

        try {
        if (cmd.isUsageHelpRequested()) {
            cmd.usage(System.out);
        }
        } catch (CommandLine.ParameterException e) {
            System.err.println("error: " + e.getMessage());
            System.err.println(e.getStackTrace());

        }
    }
}

【问题讨论】:

    标签: java command-line-arguments picocli


    【解决方案1】:

    听起来你想用subcommands 创建一个命令。您可以在 picocli 中通过使用 @Command 注释标记 method 或通过创建单独的命令类和父命令的 registering it as a subcommand 来执行此操作。如果您的子命令有很多选项,您可能希望为它创建一个单独的类。

    创建子命令后,您需要调用用户指定的子命令的逻辑。您可以使用CommandLine.parseArgs 方法手动执行此操作,但这是lot of work。我建议改用CommandLine.execute method

    execute方法会解析用户输入,处理--help--version请求,处理无效的用户输入,最后(如果用户输入有效)调用用户指定的子命令的业务逻辑.它还会返回一个退出代码。

    execute 方法要求子命令是 @Command-annotated 方法或实现 RunnableCallable@Command-annotated 类。

    以下是基于您的示例代码的示例,以子命令的形式实现。

    @Command(name = "cli", version = "1.0",
        mixinStandardHelpOptions = true,
        subcommands = {Create.class, ListObjects.class})
    public class Cli implements Runnable {
        @Option(names = {"--field1"}, required = true)
        private String field1;
    
        @Option(names = {"--field2"}, required = true)
        String field2;
    
        @Option(names={"--field3"}, required = true)
        String field3;
    
        // not needed because we have mixinStandardHelpOptions=true
        //@Option(names = {"-h", "--help"}, usageHelp = true) boolean help;
    
        public void run() {
            // business logic of the top-level cmd here
            System.out.println("hi, field1="+field1);
        }
    
        public static void main(String[] args) {
            int exitCode = new CommandLine(new Cli()).execute(args);
            System.exit(exitCode);
        }
    }
    
    @Command(name = "create", description = "create ...",
            mixinStandardHelpOptions = true, version = "1.0")
    class Create implements Callable<Integer> {
        @Option(names = {"-x", "--times"}, description = "...")
        int x;
    
        @Override
        public Integer call() {
            // business logic for "create" here...
            return ok ? 0 : 1; // exit code support
        }
    }
    
    @Command(name = "list", description = "create ...",
            mixinStandardHelpOptions = true, version = "1.0")
    class ListObjects implements Runnable {
        @Option(names = {"-x", "--times"}, description = "...")
        int x;
    
        @Override
        public void run() {
            // business logic for "list" here...
        }
    }
    

    【讨论】:

      猜你喜欢
      • 2011-10-16
      • 1970-01-01
      • 1970-01-01
      • 2019-08-27
      • 2021-12-18
      • 1970-01-01
      • 2019-11-09
      • 1970-01-01
      • 1970-01-01
      相关资源
      最近更新 更多