What is the issue with using Commons CLI?
--jason
We discussed using commons CLI to process the arguments but there
were concerns with the size of the library and also it is getting
too close to 1.0 to make large changes.
I proposed that we at least make our options follow the
convention discussed above (this would allow us to move to
commons CLI or a derivation of it in the future if needed).
PROPOSED OPTIONS FOR 1.0 RELEASE
-q --quiet ** change impacts existing users **
-v --verbose
-vv --veryverbose
-o --override ** change impacts existing users **
-h --help
-l --long ** new option to change startup
progress format **
We could still have hidden support for -help and /? but I'm not
sure if they would work with commons CLI if we were to move to it
in the future.
In regards to the vv option being more than one character,
looking at the commons CLI documentation ( http://
jakarta.apache.org/commons/cli/apidocs/org/apache/commons/cli/
Options.html ), it says the short option is a single character,
but it takes a string argument, so I think it is more of a
recommendation. If you use more than one character for the short
option you lose the ability to use the Option.getID() method that
can be useful in switch statements.
The deploy tool uses the long (--) form of options (doesn't
support a short form) but it follows the convention.
I will send another mail regarding the startup progress and
whether we should change the default format.
John
