-
-
Notifications
You must be signed in to change notification settings - Fork 3.1k
Labels
component: JabKit [cli]good first issueAn issue intended for project-newcomers. Varies in difficulty.An issue intended for project-newcomers. Varies in difficulty.
Description
Currently jabkit --version outputs nothing:
c:\git-repositories>jabkit --version
c:\git-repositories>--help outputs the version
c:\git-repositories>jabkit --help
&&& &&&&& &&&&&&&& &&&&&&&& &&&&&&&&& &&&&&&&&&
&&& &&&&& &&& &&& &&& &&& &&& &&&
&&& &&& &&& &&& &&& &&& &&& &&& &&&
&&& && && &&&&&&& &&&&&&&& &&&&&&&& &&&&&&&
&&& &&&&&&&&& &&& &&& &&& &&& &&& &&&
&&& &&& &&& &&& &&& &&& &&& &&& &&&
&&&&& &&& &&& &&&&&&&& &&& &&& &&&&&&&&& &&&
Version: 6.0-alpha.197--2025-11-24--0a9793a
Staying on top of your literature since 2003 - https://www.jabref.org/
Please report issues at https://github.com/JabRef/jabref/issues
JabKit - command line toolkit for JabRef
Usage: jabkit [-dhpv] [COMMAND]
...
c:\git-repositories>
Wish:
The version is output on the command line#
6.0-alpha.197--2025-11-24--0a9793a
Similar to jbang --version
c:\git-repositories>jbang --version
0.132.1
c:\git-repositories>
Hints
The variable is in place: org.jabref.toolkit.commands.JabKit#versionInfoRequested, but not read yet.
Read on at https://picocli.info/#_version_help for a howto for PicoCLI.
int result = commandLine.execute(args);
It might be that --version is done wrong currently and just a VersionedCommand needs to be implemented.
Run JabKit:
Modify run configuration:
Installing JabKit: https://github.com/JabRef/jabref/tree/main/.jbang#installing-and-running-jabkit-with-jbang - not required to solve the issue but helpful to understand how the outputs above are produced.
Metadata
Metadata
Assignees
Labels
component: JabKit [cli]good first issueAn issue intended for project-newcomers. Varies in difficulty.An issue intended for project-newcomers. Varies in difficulty.
Type
Projects
Status
Done