Commands doc
Maintainers usually reply within 1 day
Nobody has claimed this yet.
Assessment
- Difficulty
- 3/5
- Estimated time
- 3-5 days
- Newbie friendliness
- 35/100
- Issue type
- Documentation
- Clarity
- Mostly clear
- Activity status
- Stale
- Domain
- cli, documentation
Research direction
Start by downloading the latest All GA Features archive, extracting it, and reviewing the help output for featureUtility, springBootUtility, auditUtility, and serverSchemaGen from wlp/bin. Add documentation for the prioritized commands, ensuring the documented command-line help matches the runtime help; the issue leaves the remaining commands out of scope.
Written by the indexing model from the issue text.
Description
There are other commands than just the ones we've documented so far. I don't know how urgent it is to document them all (they all have commandline help anyway) but just so you know...
Here's the full list of the commands in OL 20.0.0.12 (the .bat files are for Windows, the ones without suffix are for UNIX/Linux, etc):
laura@Lauras-MacBook-Pro openliberty-200012 % ls wlp/bin
auditUtility binaryLog ddlGen jaxb pluginUtility.bat securityUtility.bat serverSchemaGen.bat
auditUtility.bat binaryLog.bat ddlGen.bat jaxrs productInfo server springBootUtility
batchManager client featureUtility jaxws productInfo.bat server.bat springBootUtility.bat
batchManager.bat client.bat featureUtility.bat pluginUtility securityUtility serverSchemaGen tools
To find them:
- Download the latest "All GA Features" zip from https://www.openliberty.io/downloads/
- Extract the zip file into a directory on your laptop (I created a dir called
openliberty-200012). - At a command prompt/terminal, move into Liberty's bin directory, eg:
cd openliberty-200012/wlp/bin - List the contents of the bin directory:
ls
And there you go.
You can get the help for any of the commands by typing the command's name followed by --help, eg: ./binaryLog --help. You'll see some commands you recognise in there, like server, and securityUtility.
The text in this cmdline help should match the text in the OL docs (if you add the help to the OL docs).
For extra credit (and ease of maintenance), rather than duplicating and keeping in sync, ideally someone would create something to generate the your asciidoc pages from the runtime help files according to some template you define. And then you could raise a PR to fix up the wording in the commandline help in future if you want changes to it for style or whatever.
Update on what I've said above after speaking with Alasdair:
- the online help for the commands should be good enough that we won't lose anything if not all the commands are documented
- of the commands in Open Liberty, it would be good to doc the following ones:
- featureUtility
- springBootUtility
- auditUtility
- I'll add to that the
serverSchemaGencommand, which he's previously said is useful. Info is currently only in the KC I raised an issue on the runtime to get that fixed. - all the other commands are low priority
I think if we consider the scope of this issue's work to just be those three commands, rather than all of them, it's probably ok to manually add them to the docs (rather than trying to get them generated automatically, which would take a fair amount of work, including working out a template of how the info should look etc). Leave the rest of the commands (if there's a need in future, the info is in the online help anyway).
- Dominant language
- No language data
- Stars
- 14
- Forks
- 58
- Avg merge
- 1h 4m
- Merged PRs (30d)
- 21
Getting set up
- No Dockerfile or Docker Compose file
- No pull request template
- Read the contributing guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
More from OpenLiberty/docs
-
source mismatchOpen
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
OpenLiberty/docs#8579 ·
Maintainers usually reply within 1 day
-
Jandex extended pathOpen
Difficulty 2/5 1-3 hours Newbie friendliness 74/100
OpenLiberty/docs#8451 · 1 comment ·
Maintainers usually reply within 1 day
-
CVE update for 26.0.0.10Possibly taken @ramkumar-k-9286 claimed this 18 days ago. Open26.0.0.10
OpenLiberty/docs#8563 · 5 comments · 1 assignee ·
Maintainers usually reply within 1 day
-
26.0.0.11
Difficulty 5/5 Over a week Newbie friendliness 25/100
OpenLiberty/docs#8548 ·
Maintainers usually reply within 1 day
-
26.0.0.12
Difficulty 4/5 3-5 days Newbie friendliness 45/100
OpenLiberty/docs#8529 · 1 comment ·
Maintainers usually reply within 1 day
All issues in OpenLiberty/docs
Similar issues
-
area:config area:security bug good first issue platform:linux platform:windows priority:medium
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
Maintainers usually reply within 1 day
-
gdsa opencode: keep-alive cleanup trap fails with 'keepalive_pid: unbound variable'Possibly taken @darribas claimed this today. Open
Difficulty 2/5 1-3 hours Newbie friendliness 85/100
-
documentation good first issue help wanted
Difficulty 2/5 1-3 hours Newbie friendliness 82/100
steerion-labs/bounded-agent-runtime#92 ·
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
Yeachan-Heo/oh-my-codex#3822 ·
Maintainers usually reply within 1 day
-
ai-generated
Difficulty 1/5 Under an hour Newbie friendliness 88/100
Maintainers usually reply within 1 day