Hacktoberfest 2026: los issues que los mantenedores marcaron para octubre, abiertos y aptos para principiantes. Explorar issues de Hacktoberfest

Commands doc

Abierto
  • ¿Algo no está bien?
#3,314 1 comentario 0 reacciones 0 asignados Ver en GitHub

Los mantenedores suelen responder en 1 día

Nadie ha tomado este issue todavía.

Evaluación

Dificultad
3/5
Tiempo estimado
3-5 días
Aptitud para principiantes
35/100
Tipo de issue
Documentación
Claridad
Bastante claro
Estado de actividad
Estancado
Área
cli, documentation

Línea de trabajo

Comienza descargando el archivo más reciente de All GA Features, extrayéndolo y revisando la salida de ayuda de featureUtility, springBootUtility, auditUtility y serverSchemaGen de wlp/bin. Añade documentación para los comandos priorizados, asegurándote de que la ayuda de línea de comandos documentada coincida con la ayuda en tiempo de ejecución; el issue deja los comandos restantes fuera del alcance.

Escrito por el modelo de indexación a partir del texto del issue.

Descripción

epic

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:

  1. Download the latest "All GA Features" zip from https://www.openliberty.io/downloads/
  2. Extract the zip file into a directory on your laptop (I created a dir called openliberty-200012).
  3. At a command prompt/terminal, move into Liberty's bin directory, eg: cd openliberty-200012/wlp/bin
  4. 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 serverSchemaGen command, 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).

Lenguaje dominante
Sin datos de lenguaje
Estrellas
14
Forks
58
Merge medio
1 h 4 min
PR fusionados (30 d)
21

Preparar el entorno

Primeros pasos

  1. Lee el issue completo y luego la guía de contribución del proyecto.
  2. Comenta en el issue que vas a ocuparte — evita que dos personas hagan lo mismo.
  3. Haz un fork del repositorio y trabaja en una rama.
  4. Abre un pull request que haga referencia al número del issue.

Más de OpenLiberty/docs

Todos los issues de OpenLiberty/docs

Issues similares

Más issues de CLI

Recibe los nuevos issues en tu correo

Un resumen breve de issues de GitHub para principiantes.