Open tinwelint opened 8 years ago
I think this is because @Arguments
is supposed to be used over a List<String>
attribute - this way it passes all the arguments to the list and it is left for the developer to make error checks and then use them in his own way.
Refer #6 for more details.
I have a command with two arguments:
when building a CLI for that command I get exception:
The two arguments doesn't conflict. Instead this looks to be an issue at https://github.com/airlift/airline/blob/master/src/main/java/io/airlift/airline/model/ArgumentsMetadata.java#L48 where that condition looks to be negated... i.e. it will always report conflict if there are more than one argument defined.