build-get_starter
Generate starter build files for a new Exeris application: a pom.xml or package.json pre-wired with annotation processors, codegen goals and tested dependency versions.
Instructions
Return the build files for a NEW Exeris application and write none: for 'backend', a pom.xml whose parent is exeris-app-parent and which depends on exeris-app-starter; for 'frontend', a package.json with @exeris/codegen-ts and its exeris-gen generate script; for 'both', the two under backend/ and frontend/. Ask this BEFORE hand-writing a pom.xml or package.json for an Exeris application: the starter already wires the annotation processor, the codegen goals and the dependency set. Every version comes from the exeris-app-bom the bridge was released with, which names one tested tooling + kernel + SDK triple; the tool reports it as bomVersion and triple. supplied lists what the application still adds itself, starting with the JDBC driver. Needs no project: it reads bundled data only, and you write the files with your own tools.
Tool call template
Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.
{
"id": 1,
"jsonrpc": "2.0",
"method": "tools/call",
"params": {
"arguments": {
"variant": "<variant>"
},
"name": "build-get_starter"
}
}Input Schema
| Name | Required | Description | Default |
|---|---|---|---|
| variant | Yes | Which application to start: 'backend' (Maven), 'frontend' (npm), or 'both' (a backend and a frontend that generates from the backend's build). |