Installing qBits

Use a real component release and verify its dependency graph in your host.

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.

Bash

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.