Hola Izio! > Conversely, JCommander has a very low learning curve.
sure I'm JCommander user myself, but that are the reason why that approach cannot universally applied * it's not complete (yet) since it doesn't support Java-alike dynamic options such as `-Dproperty=value` (they need to be collected in a Properties/Map instance) * it forces all parameters to be collected in POJOs - that is not universally good (hey could be used to be passed in a pom.xml); * it doesn't support Posix parser; * wrong converters binding can be detected at runtime only - since they are expressed in annotations, nothing can be done from the compiler side; * it would be useful performing blocking actions when detecting some parameters, i.e. like --help that prints the usage message and exit; * ... shall I continue? :) > The example you provided is good enough, but it is still far away in terms > of learning curve. UH... Seriously? Being fluent-APIs should be at least easier of current [cli] APIs... Thanks for the feedbacks! -Simo http://people.apache.org/~simonetripodi/ http://simonetripodi.livejournal.com/ http://twitter.com/simonetripodi http://www.99soft.org/ --------------------------------------------------------------------- To unsubscribe, e-mail: dev-unsubscr...@commons.apache.org For additional commands, e-mail: dev-h...@commons.apache.org
