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.
This artifact provides a bill of materials (BOM) for remoting based EJB usage. Importing this bom into your project will give you the maven artifacts you need to perform remote EJB calls.
Weld Core "bill of materials" which can be imported by any project using the Weld implementation of
CDI.
It provides dependency management for the implementation.
Weld APIs "bill of materials" which can be imported by any project using the Weld implementation of
CDI. It provides dependency management for the developer APIs and SPIs, as well as container integrator SPIs
Module that provides all the APIs versions provided by the Mule Runtime for a particular runtime version. Users of the APIs should use this BOM when depending on any Mule API.
A BOM project that provides a set of Mule Runtime Libraries (a subset API libraries) that can work in a separate module layer/class loader than the rest of Mule Runtime Libraries
This artifact provides a bill of materials (BOM) for remoting based EJB usage.
Importing this bom into your project will give you the maven artifacts you need
to perform remote EJB calls.
AS 7 console "bill of materials" which can be imported by any project
providing extensions to the console. It provides dependency management for the developer APIs and SPIs.
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).