[
https://issues.apache.org/jira/browse/DAFFODIL-2477?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17342624#comment-17342624
]
John Interrante commented on DAFFODIL-2477:
-------------------------------------------
I confirmed -V still needs an argument, although the behavior differs depending
on whether -V is the last argument on the command line. If -V comes before -s,
the CLI treats-s as the mode and errors out with the message:
{code:java}
[error] Bad arguments for option 'validate': '-s' - Unrecognized ValidationMode
-s{code}
If -V comes last (nothing after it), then the CLI errors out with the message:
{code:java}
[error] Bad arguments for option 'validate': '' - you should provide exactly
one argument{code}
The bug appears to be within validateConverter in Main.scala, but looks like
it'd need some time to fix it. Want to leave this bug alone for a fix later or
change the CLI help to say MODE is required?
> --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)
