Hi Simone, I don't know how others make use of CLI, what I'm going to discuss is only my personal point of view. I have to do with the command line stuff one time per project (more or less), and I have to admit that the CLI api (even though is a good one) is every time hard to apply. This is probably due the sporadic use. Conversely, JCommander has a very low learning curve. The example you provided is good enough, but it is still far away in terms of learning curve.
Twitter :http://www.twitter.com/m_cucchiara G+ :https://plus.google.com/107903711540963855921 Linkedin :http://www.linkedin.com/in/mauriziocucchiara Maurizio Cucchiara On 26 December 2011 22:35, Simone Tripodi <simonetrip...@apache.org> wrote: > Hi all guys, > I have been experimenting a new set of CLI APIs outside the ASF, > taking the best from existing CLI and some other non-ASF libraries, > mainly Cédric's JCommander[1], the purposes are: > > * using fluent APIs; > * simplify the Options building; > * reducing the number of involved components; > * triggering actions when options are parsed; > > A simple (not working) APIs usage can be found on the GitHub's space[2]. > > So, I would much more than happy to move the effort to [commons] and > donate the prototype, if people think it would be a worth give a try > to innovate [cli]. > Otherwise, I will have to finalize it outside the ASF. > Feedbacks are welcome, many thanks in advance! > -Simo > > [1] http://jcommander.org/ > [2] http://s.apache.org/xS > > 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 > >
