Well, certainly in the first instance it would be good to know how much of the existing annotation functionality works as-is from Java.
On Tue, May 29, 2018 at 5:29 AM, Romain Manni-Bucau <rmannibu...@gmail.com> wrote: > Do you think groovy community could try to extract it and do a PR to cli > project? I already did it like 5 times (+ tomitribe-cli work) and would be > happy to see some convergence here. Cli is a strong base for the parsing > but api is too raw :(. > > > Le lun. 28 mai 2018 20:46, Paul King <pa...@asert.com.au> a écrit : > >> I've mentioned it on the cli dev list before: >> >> https://markmail.org/message/45jgonianj4sw7i4 >> >> You can probably use it all directly from Java apart from the >> Closure-based converters (which are also possible from Java just a big >> uglier). We could easily provide a lambda overload these days if there was >> interest. >> >> Cheers, Paul. >> >> >> On Tue, May 29, 2018 at 4:31 AM, Remko Popma <remko.po...@gmail.com> >> wrote: >> >>> Personally, I would invite everyone using Commons CLI to migrate to >>> picocli <https://github.com/remkop/picocli>. >>> But I may be biased... :-) >>> >>> Remko >>> >>> On Tue, May 29, 2018 at 2:06 AM, Romain Manni-Bucau < >>> rmannibu...@gmail.com> wrote: >>> >>>> Hi guys >>>> >>>> Saw you added some annotations to write a cli in groovy cli, did you >>>> try (or do you plan) to propose it to commons cli? It would be an awesome >>>> addition which affects more than groovy users IMHO and could unify part of >>>> the specific api you created. >>>> >>>> Romain >>>> >>> >>> >>
