[
https://issues.apache.org/jira/browse/CLI-141?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12518649
]
Brian Egge commented on CLI-141:
--------------------------------
I agree with the hasArg change. My preference for serializable classes is to
use the number which would be generated by serialver. This way, if someone is
already serializing this class, it won't break their code if they don't upgrade
both the client and server at the same time.
Other people prefer to start a 1L and increment each time the public interface
changes. I don't know if Apache has a standard one way or the other.
> CLI Option reports arguments incorrectly on toString()
> ------------------------------------------------------
>
> Key: CLI-141
> URL: https://issues.apache.org/jira/browse/CLI-141
> Project: Commons CLI
> Issue Type: Bug
> Components: CLI-1.x
> Affects Versions: 1.1
> Reporter: Henning Schmiedehausen
> Priority: Minor
> Attachments: option.patch
>
>
> The Option class contains some logic around the "hasArg" boolean that seems
> to be cruft and no longer works correctly. There is no need for this boolean
> anymore and its only usage could be replaced with hasArg() / hasArgs() calls.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
