The specific exceptions now reside in the o.a.c.cli2.impl package. These should be in the o.a.c.cli2 package so caller's can catch the specific Exception if required.
I do not see the need to catch a specific exception. I would just catch OptionException, display the error message and then print the help/usage statement.
Any real world reasons for catching the specific exceptions? If there is no reason then they are fine where they are. We could always remove them and only throw the CLIException (OptionException seems like the wrong name for it). This is of course dependant on where Exceptions are currently thrown.
The construction phase doesn't throw Exceptions. We probably need to throw for a validation exception when defaults are specified and are not valid.
Comments?
-John K
--------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
