The Plexus IoC container API and its default implementation.
📦 Bill of Materials (BOMs)
BOMs are special artifacts that define dependency versions for a set of related artifacts.
Import a BOM in your project to manage consistent versions across related dependencies.
Quarkus Universe platform aggregates extensions from Quarkus Core and those developed by the community into a single compatible and versioned set that application developers can reference from their applications to align the dependency versions
Quarkus Universe platform aggregates extensions from Quarkus Core and those developed by the community into a single compatible and versioned set that application developers can reference from their applications to align the dependency versions
The BOM declares all internal and appformer dependency versions in dependencyManagement.
KIE modules should _not_ directly import this BOM and instead use kie-parent and import specific KIE user BOMs.
Quarkus universe aggregates extensions from Quarkus Core and those developed by the community into a single compatible and versioned set that application developers can reference from their applications to align the dependency versions
The parent with dependencies imports the KIE third party BOM, all user BOMs and adds the default test-scoped dependencies.
This is a temporary POM which should eventually removed once all the downstream projects migrate to kie-parent + user BOMs.
The parent with dependencies declares all dependency versions in dependencyManagement.
All modules extend this parent, except for the boms (which are used here).
The parent contains all metadata (including plugins) including dependency versions. All modules, except for user BOMS,
should (transitively) inherit from this parent.
The BOM declares all (internal + 3rd party) dependency versions in dependencyManagement.
KIE modules should _not_ directly import this BOM and instead use kie-parent and import specific KIE user BOMs.