The current pattern for creating optional parameters (as described at
http://jewelcli.sourceforge.net/usage.html ) seems like a bit of a hassle.
Perhaps this could be more elegantly implemented with a 'required' field on
the @Option annotation (default 'true')?
Nobody/Anonymous
None
None
Public
Copyright © 2009 Geeknet, Inc. All rights reserved. Terms of Use