commons-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Henning Schmiedehausen (JIRA)" <>
Subject [jira] Commented: (CLI-142) CLI Parser is not very extension friendly
Date Mon, 06 Aug 2007 14:25:59 GMT


Henning Schmiedehausen commented on CLI-142:

BTW: If you are looking for an use case, here it is:

I have a dynamic Task executor, that has a fixed set of options (list, info, run) and loads
an additional set of options depending on the service name given as an argument to list/info/run.
So as soon as one of these three has been encountered, I use processOptions to dynamically
query the task in question about its options and add it to the running parser.

(And I do it over JMX, hence I need serializable classes.  ;-) )

> CLI Parser is not very extension friendly
> -----------------------------------------
>                 Key: CLI-142
>                 URL:
>             Project: Commons CLI
>          Issue Type: Improvement
>          Components: CLI-1.x
>    Affects Versions: 1.1
>            Reporter: Henning Schmiedehausen
>         Attachments: parser.patch
> The Parser class is not really extension friendly.
> - cmd is private, should either be protected or have a getter/setter pair
> - options and requiredOptions should have getter/setters (requiredOptions depends on
> - processProperties is private, should be protected
> - processOptions is private, should be protected
> - 

This message is automatically generated by JIRA.
You can reply to this email to add a comment to the issue online.

View raw message