Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

Consider replacing JCommander with picocli for the CLI part #16

Open
AuPath opened this issue Apr 4, 2024 · 1 comment
Open

Consider replacing JCommander with picocli for the CLI part #16

AuPath opened this issue Apr 4, 2024 · 1 comment
Assignees
@AuPath
Labels
enhancement New feature or request

Comments

@AuPath
Copy link
Collaborator

AuPath commented Apr 4, 2024

picocli offers several improvements over JCommander:

  • Automatic documentation generation (man page, html ...).
  • Easier to unit test the CLI itself. We had some problems in the past related to this.
  • Applications built with picocli can be natively compiled with GraalVm native images. We do not strictly need this but it is interesting.

@marioscrock, what do you think?
@AuPath AuPath added the enhancement New feature or request label Apr 4, 2024
@AuPath AuPath self-assigned this Apr 4, 2024
@marioscrock
Copy link
Member

Agree! I chose JCommander because it was the recommended and easier library many years ago, picocli seems a good alternative with a very active community (link) and I like that it supports native compilation.

@AuPath AuPath mentioned this issue Apr 5, 2024
Merged
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@AuPath AuPath

Labels
enhancement New feature or request
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
2 participants
@marioscrock @AuPath