On 12/17/12 02:49 PM, Shawn Walker wrote:
line 1060: s/;//
lol
Can you provide some example output for each case?
You won't see them coming through the client's checking code but I
triggered them artificially and this is how it looks like (after I found
a few more bugs in this piece of code):
incompatible:
InvalidOptionException: The '_new_be' and '_be_name' option may not be
combined
repeated option:
InvalidOptionException: Option '_backup_be' repeated
required option:
InvalidOptionException: '_new_be' may only be used with '_be_name'
xor option:
InvalidOptionException: Either '_backup_be' or '_be_name' must be specified
generic:
InvalidOptionException: invalid option(s): _backup_be _be_name
custom message:
InvalidOptionException: The bobcat is crazy: _backup_be _be_name
(ignore the logical connection between the options, it's just for
showing the message)
We would be able to use these messages in the CLI but the use is very
limited since the testing is very basic and we would just remove a few
lines of checking code and replace it with exception analysis later.
This is more intended for third party clients using the API directly.
Erik
_______________________________________________
pkg-discuss mailing list
pkg-discuss@opensolaris.org
http://mail.opensolaris.org/mailman/listinfo/pkg-discuss
