Guess much of this comes down to taste. And tbh, I think most of our committers prefer writing Java over POSIX man pages :) Also, the one who volunteers to actually do the work, after (lazy) consensus, gets to pick the tools too. :)
Segway: I'm hoping you'll pick up our horrible security framework, you had some really nice ideas there around Shiro. Another idea surfaced in our hallway discussions during Community Over Code, was to use OPA to enforce security policies in Solr. I never thought that would be an option, but would be interesting to evaluate alongside Shiro? Jan > 15. okt. 2026 kl. 01:32 skrev Gus Heck <[email protected]>: > > On Wed, Oct 14, 2026 at 7:15 PM Eric Pugh via dev <[email protected]> > wrote: > >> I’d like to see us get to done done on Picocli. And then save looking at >> another cli tool for the Solr 12 timeframe! >> >> > I agree of course. As I said, I am late to the party, but the only thing > better than code as the source of truth is documentation as the source of > code. > > With DocOpt your code to parse Args is: > > Map<String, Object> result = new Docopt(usageStr).parse(args); > > That's it. > > usageStr is a POSIX compliant help text (loaded from a text file or > wherever else you might like). Ref guide could just embed the posix help > text. There is a whole ecosystem of implementations of this tool in many > different languages, so if we have any python tools, or other code in > secondary languages other than java they could also use the same system. > > https://www.youtube.com/watch?v=pXhcPJK5cMc --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
