Skip to content

SOLR-17697 Use picocli instead of commons-cli#3254

Draft
janhoy wants to merge 4 commits intomainfrom
jira/SOLR-17697-picocli
Draft

SOLR-17697 Use picocli instead of commons-cli#3254
janhoy wants to merge 4 commits intomainfrom
jira/SOLR-17697-picocli

Conversation

@janhoy
Copy link
Copy Markdown
Contributor

@janhoy janhoy commented Mar 11, 2025

https://issues.apache.org/jira/browse/SOLR-17697

This PR is just a way to visualize the status of the feature branch jira/SOLR-17697-picocli.
Create PRs targeting that branch to tackle individual tasks, and then merge into this feature branch once done.

Tasks/milestones:

  • Add framework
  • Implement POC for a few initial tools, in parallel with commons-cli
  • Solve option inheritance / MixIn
  • Solve option mutual exclusivity
  • Solve value-fallback to ENV
  • Document in RefGuide - Auto generate?
  •  All tools covered
  • BATS tests green
  • Proof read Usage helps
  • Remove commons-cli

@xtenzQ
Copy link
Copy Markdown
Contributor

xtenzQ commented Mar 21, 2025

Actually, I'd like to try to implement PoC for few initial tools.

upd: oh, I didnt notice there is a PR created for this

@janhoy
Copy link
Copy Markdown
Contributor Author

janhoy commented Mar 21, 2025

upd: oh, I didnt notice there is a PR created for this

Yea, there's an in-progress exploration taking place, feel free to join the discussion about it or POC for yourself on how to solve various issues that arise. We're still trying to land on the most elegant way to introduce things, and I plan to dial down the ambitions for the other PR to do bare minimal for one or two tools, and perhaps the "start" tool. Eventually, when we start getting the grip on how things should flow, it will be easier to jump in and implement PRs for new tools, targeting this branch.

@janhoy janhoy force-pushed the jira/SOLR-17697-picocli branch from 4ddb026 to 97a673e Compare April 5, 2026 12:45
@janhoy janhoy force-pushed the jira/SOLR-17697-picocli branch from 97a673e to cb41a69 Compare April 5, 2026 12:50
@epugh
Copy link
Copy Markdown
Contributor

epugh commented Apr 5, 2026

Let's get this into main as soon as possible!!!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants