Yup, updating CLICommand in the core is not in the table. Too much effort
with low benefit, CLICommand implementation in Jenkins is already a
"sub-command" from the user and developer standpoint.

When I mentioned Jenkins core, I rather meant the default "java -jar
jenkins.war" entry point, and a similar one for remoting. That could be
updated, and for remoting it could actually help to improve UX. But, still,
not very high on the priority list.


On Mon, Nov 23, 2020, 23:23 Jesse Glick <jgl...@cloudbees.com> wrote:

> picocli seems appropriate for new development. It is integrated with
> Quarkus, too. I doubt we would want to rewrite existing Jenkins
> features using args4j; in particular, `CLICommand` hard-codes it (we
> could not switch compatibly).
>
> --
> You received this message because you are subscribed to a topic in the
> Google Groups "Jenkins Developers" group.
> To unsubscribe from this topic, visit
> https://groups.google.com/d/topic/jenkinsci-dev/jTkOpdZ7z1s/unsubscribe.
> To unsubscribe from this group and all its topics, send an email to
> jenkinsci-dev+unsubscr...@googlegroups.com.
> To view this discussion on the web visit
> https://groups.google.com/d/msgid/jenkinsci-dev/CANfRfr0%2BvyvbovgW4oUESjNMhpsDwoKQ8cy%3D9cYU82nAVOGhdw%40mail.gmail.com
> .
>

-- 
You received this message because you are subscribed to the Google Groups 
"Jenkins Developers" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to jenkinsci-dev+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/jenkinsci-dev/CAPfivLBSx4N2%3Dw36qZvLaf5Y0Fkd%3D2Go0688bpC5cW0Dpxs0ag%40mail.gmail.com.

Reply via email to