Build Your First QBit for QQQ 4.0

Customize a real template, register its producer, and test it in a host application.

Choose the template

Use qbit-template-application for navigation, tables, processes, and widgets; qbit-template-data for reference-data scaffolding; or qbit-template-extension for customizers. Check the source version against release status.

Customize the generated project

Create your repository from the template. Rename Maven group/artifact coordinates, the Java package, Example classes, and metadata names. Use the IDE rename tools and check string-based references. Read the template's getting-started guide for its actual file layout. There is no required qbit.json manifest or customize.sh script in these templates.

Build and integrate

Bash

mvn clean verify

Implement the scaffold behavior and meaningful tests. The extension customizer starts as an example; a passing compile does not prove it changes records. The data template prefixes table names, but multiple instances also need unique process and possible-value-source names.

Add your built component as a dependency of a test host. Define the backend, instantiate the component-specific config, and invoke its producer. The data template uses ExampleDataQBitProducer.withConfig(...).produce(qInstance, "example-data"). Validate the complete QInstance and exercise the component's action or process.

Publish deliberately

Choose your own component version and configured Maven publication destination. Preserve LICENSE and NOTICE, and document exact supported QQQ versions, required backends, configuration, and integration tests. Do not publish the template's example coordinates or claim every production QBit is certified for 4.0.

The build-parent target com.kingsrook:qbit-build-parent:2.0.0 follows final QQQ publication. Verify availability before adopting it. See Creating QBits.