JoinedWorkz 1.3.81 improves the developer feedback loop, makes generation contracts more deterministic and adds independently released Maven Archetypes for runnable Spring Boot and Spring Boot with Quasar starter projects.
Maven Archetypes 1.0.0 create a runnable Spring Boot project or a full-stack project with an experimental Quasar frontend. H2 works without Docker; PostgreSQL and embedded or standalone frontend delivery are selectable alternatives.
Platform profiles declare configuration contracts. Invalid values stop generation, while Maven reports stable diagnostics for unknown and unused properties after all models have been processed.
Outlet paths, package overrides, effective package names, generated operation names and configuration aliases now have explicit validation and deterministic precedence.
The release documents and verifies schema-migration modes, ID generation, integer-coded enum persistence, controller composition, request headers and richer OpenAPI type and example handling.
Page Conditions replace Page States, application widgets use componentRef,
and action validation catches invalid aliases and unsupported command shapes before
emitting JavaScript.
Current and previous documentation can be selected explicitly. A machine-readable version catalogue helps humans and AI agents resolve the documentation matching a project's JoinedWorkz release.
This release deliberately rejects several ambiguous or invalid inputs that older generation paths could accept. Review the complete upgrade guide before regenerating a production project. In particular:
states with Boolean conditions;deleteInstance for the opinionated item-deletion method type;The detailed upgrade guide explains compatibility aliases, changed behavior and safe verification steps. Do not infer a migration only from generated-file diffs.
Archetype versions are independent from JoinedWorkz versions. Maven generation does not require Studio or a Studio license.