This is a small repository which holds some JBang utilities.
All commands listed will have a hidden generate-completion
sub-command for auto-completion in bash or ZSH.
This simple utility parses a surefire and failsafe reports and by default just outputs some totals.
The simplest way to install the command is with the JBang Alias.
jbang app install parse-surefire-report@jamezp
To update the application:
jbang build --fresh parse-surefire-report@jamezp
The simplest way to install the command is with the JBang Alias.
jbang app install jdk-manager@jamezp
To update the application:
jbang build --fresh jdk-manager@jamezp
Listing the available JDK’s for download:
jdk-manager list
LTS Versions for temurin
8
11
17
*21
STS Versions for temurin
16
18
19
20
22
23
24
Early Access Versions for temurin
24
25
Listing locally installed JDK’s from this tool:
jdk-manager list --local IBM Corporation 23.0.1 (2024-10-15): /home/jperkins/.jdk-manager/semeru/jdk-23 Eclipse Adoptium 17.0.13 (2024-10-15): /home/jperkins/.jdk-manager/temurin/jdk-17 Eclipse Adoptium 21.0.5 (2024-10-15): /home/jperkins/.jdk-manager/temurin/jdk-21 Eclipse Adoptium 23.0.1 (2024-10-15): /home/jperkins/.jdk-manager/temurin/jdk-23 Eclipse Adoptium 24-beta (2025-03-18): /home/jperkins/.jdk-manager/temurin/jdk-24 Eclipse Adoptium 25-beta (2025-09-16): /home/jperkins/.jdk-manager/temurin/jdk-25 Temurin 1.8.0_432 (null): /home/jperkins/.jdk-manager/temurin/jdk-8
Installing a JDK
jdk-manager install 21
Setting the JAVA_HOME
based on the result of a local JDK.
export JAVA_HOME="$(jdk-manager info -d -p java.home 21)"
This simple utility creates a server socket and echos the data received to stdout
.
The simplest way to install the command is with the JBang Alias.
jbang app install echo-server@jamezp
To update the application:
jbang build --fresh echo-server@jamezp
This is a utility, specifically designed for Red Hat JIRA, which creates a JIRA based on a GitHub Pull Request. It is useful when there is a need to create a JIRA for a dependabot pull request.
It requires two files be present on your local file system in your home directory, preferably with 0600 permissions on the files:
-
.github
-
.jira
The .github
file must have an entry for oatuh
where the value is simply a GitHub token. This file and property name
is adopted from https://hub4j.github.io/github-api/.
The .jira
file must have the following two properties:
-
username
where the value is your JIRA username -
token
where the value is a token you must create for your JIRA user.
The simplest way to install the command is with the JBang Alias.
jbang app install jira-from-pr@jamezp
To update the application:
jbang build --fresh jira-from-pr@jamezp
There are 3 required parameters:
Argument | Description |
---|---|
|
The GitHub organization where the pull request is located. |
|
The GitHub repository where the pull request is located. |
|
The JIRA project at https://issues.redhat.com |
jira-from-pr -o resteasy -r resteasy -p RESTEASY 4686
You can pass more than one pull request to the command to allow additional pull requests to be updated with the JIRA. Only the first pull request is used to create the JIRA. Each additional pull request is simply updated with the JIRA information and a link to the pull request is added to the JIRA.
Tip
|
Use this option when you have the same version upgrade on two different branches. |
For details on additional parameters execute:
jira-from-pr -h
This is a simple utility that allows you to query archive files. It allows you to recursively inspect files. This can be useful for things like WAR’s where there may be embedded JAR’s you want to see the contents of.
The simplest way to install the command is with the JBang Alias.
jbang app install zip-util@jamezp
To update the application:
jbang build --fresh zip-util@jamezp