QBit Development

QBit development

QQQ 4.0 release. Final 4.0.0 is available. See QQQ 4.0 for release scope and migration guidance.

Choose a template

Template	Purpose
Application	Tables, processes, navigation, and widgets
Data	Reference data and sync scaffolding
Extension	Framework customizers and infrastructure behavior

Use the repository template feature, then rename Maven coordinates, Java packages, classes, and metadata names. Follow its getting-started guide and run mvn clean verify on the generated project. These are scaffolds; supply business rules, integration credentials, tests, and host configuration.

Register in the host

QBits use a producer and a component-specific config. The data template demonstrates withConfig followed by produce(qInstance, "example-data"). The host must define the backend before production and validate the assembled QInstance. Prefixing tables alone is insufficient for multiple instances: process names, possible-value sources, and references must also be unique.

Versions and publication

Choose a real released dependency version and verify its compatibility with your host. The 4.0 build-parent target is com.kingsrook:qbit-build-parent:2.0.0, published after final core. Check release status before using it. Existing production QBits are outside this release train's certification.

Publish your own component through its configured Maven release process. The template example artifacts are not published components, and no qbits-registry registration is required by the framework. Preserve each component's LICENSE and NOTICE.

Choose a component release

Confirm that the component exists, has a published artifact, and documents compatibility with your QQQ version. Use its actual Maven coordinates and an exact version. The QQQ BOM aligns core modules; it does not certify or automatically install every QBit.

Integrate deliberately

Add the documented Maven dependency, instantiate the component's configuration and producer, and register its metadata after the required host backends are defined. Run QInstanceValidator over the complete instance.

mvn dependency:tree
mvn clean verify

Inspect mixed QQQ versions and test the component's real behavior, permissions, and persistence in the host. qctl qbit add is not the installation contract for the current native CLI.

The 4.0 QBit build-parent target is com.kingsrook:qbit-build-parent:2.0.0, following final core publication. Check release status before selecting that parent. Production QBits remain a separate migration effort.