[
https://issues.apache.org/jira/browse/DAFFODIL-2477?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17342683#comment-17342683
]
Steve Lawrence commented on DAFFODIL-2477:
------------------------------------------
Note that if we keep it with the current behavior and document the arg as
mandatory, we could always make it optional in the future and it would still be
backwards compatible. So it doesn't exclude that capability in the future if we
want it. Still not sure it adds that much aside from extra complexity though.
> --validate option requires parameter
> ------------------------------------
>
> Key: DAFFODIL-2477
> URL: https://issues.apache.org/jira/browse/DAFFODIL-2477
> Project: Daffodil
> Issue Type: Bug
> Components: CLI
> Affects Versions: 3.0.0
> Reporter: Steve Lawrence
> Priority: Minor
> Labels: beginner
>
> The CLI --validate flag allows an optional "mode" argument to specify whether
> to have full, limited, or no validation. If mode is not specified, it
> defaults to no validation.
> As of Daffodil 3.0.0, this appears to be broken and the mode parameter is
> required. If you do not specify a mode, you get the error:
> {code:java}
> [error] Bad arguments for option 'validate': '' - you should provide exactly
> one argument for this option{code}
> We need to fix this to make it optional again, or if that isn't possible for
> some reason, make it so the documentation is changed to make it clear that
> mode is a required argument.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
