jgen, not app-genapp-gen / gen.sh generator is deprecated. The current, supported generator is jgen — a pure-Java, blueprint-driven tool. Everything below uses jgen. See jgen in depth and writing blueprints.
What you’ll need
- Java 17+ — jgen and the generated services are Java/Spring Boot.
- Maven (
mvn) — to build jgen and the generated project. - git and a shell —
bash,zshor PowerShell.
(No Node required — jgen is a Java program.)
1 · Install jgen
brew install ajapros/jgen-tap/jgen # macOS / Linux (or: jbang app install jgen@rajakolluru/chenile-gen)
brew install ajapros/jgen-tap/stm-cli # optional: diagrams and test cases from states XML
To build JGen from source instead: git clone https://github.com/rajakolluru/chenile-gen.git, cd chenile-gen,
make clean all, then source setpath.sh, which puts jgen.sh on your PATH. See
Install JGen. JGen and stm-cli are released on their own cadence; jgen
--version shows which Chenile version generated projects target.
Using Claude? Install the Chenile plugin for Claude. Claude then
follows Chenile’s house rules and uses JGen blueprints when it writes code:
/plugin marketplace add ajapros/chenile-claude-plugins, then /plugin install chenile@chenile-plugins.
2 · (Optional) create a local config
jgen ships sensible defaults (package com.mycompany.myorg, version 0.0.1-SNAPSHOT, output ./output). To customise them for your company:
jgen -e # emits the default config into ./config
Edit config/config.json — set company, org and the Chenile version. jgen offers any file in config/ as a choice at startup, and resolves placeholders like ${defaultVersion} from it.
3 · Generate a service
Run jgen with no arguments for the interactive flow:
jgen
# 1) pick your config (or the bundled default)
# 2) choose the blueprint: chenile-service
# 3) service name: orders
# accept the defaults for version (0.0.1-SNAPSHOT) and output (./output)
# jpa: y security: n cloudSwitch: n MCP: n
You now have output/orders/ — the service, split into orders-api (the definition) and orders-service (the implementation).
Prefer scripted/non-interactive generation?
jgen -g chenile-service -o orders.jsonwrites a sample input file showing exactly which fields the blueprint expects; edit it, then runjgen -f orders.json.
4 · Generate a mini-monolith to host it
A service module is a library — it’s deployed by a mini-monolith. Generate one and add your service as a dependency:
jgen
# choose the blueprint: minimonolith
# monolith name: ordersdeploy
# add "orders" under the dependencies prompt (and enable H2 console / query controller if you like)
This produces output/ordersdeploy/ — a runnable Spring Boot deployable that hosts one or more Chenile services.
5 · Build & run
cd output/orders && make build # builds the api + service libraries (mvn install)
cd ../ordersdeploy && make build # builds the deployable
cd ../ordersdeploy && make run # starts it — call your endpoint with the scripts in scripts/
More blueprints
jgen ships a blueprint for almost every kind of Chenile module — a workflow service, a MyBatis query, an interceptor, a batch job, integration tests, even a blueprint that generates blueprints. Explore them all:
jgen in depth
Every built-in blueprint, the interactive vs. file-driven flows, config and template mechanics — with a live blueprint picker.
Write your own blueprint
The anatomy of a blueprint and how to scaffold a new one with the jgen-blueprint blueprint.
Understand the split
What lives in the api vs service module, and why consumers only ever depend on the api.
Watch the series
Prefer video? The same story, in short episodes with live demos.
jgen -g <blueprint> to see that blueprint's exact fields.