Developer tools · reports · Early development
Inkstadt
Developer tooling for JasperReports templates, starting with local JRXML migration assessment.
- My contribution
- Development of the Java and TypeScript tooling foundation.
- Built with
- Java · TypeScript · VS Code · LSP
Start by understanding the templates
Moving a report estate between formats starts with knowing what is in it. The current CLI inventories JRXML files and migration review points, with text and JSON output and deterministic exit codes for CI.
Text as the source of truth
The project brings together a Java monorepo, a language-server sidecar and a VS Code extension. The extension can start the sidecar for JRXML files; the sidecar implements initialization and a diagnostic ping.
Build a verifiable foundation
A license-tracked corpus of JRXML version pairs, quality gates and startup benchmarks support the early implementation. Assessment findings are format heuristics, not proof that a report will compile or render.
What comes next
Verified conversion, engine-backed preview and richer editing are planned. The project is not yet released, and these planned capabilities are not part of the current editor.