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.
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.
This artifact provides a bill of materials (BOM) for remoting based EJB for clients which require 100% API compatiblity with EAP 7.0 and earlier releases. It is recommended to use the primary wildfly-ejb-client-bom if possible.
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 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).
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
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.
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
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
Apache Geode provides a database-like consistency model, reliable transaction processing and a shared-nothing architecture to maintain very low latency performance with high concurrency processing
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.
This artifact provides a bill of materials (BOM) for remoting based EJB for clients which require 100% API compatiblity with EAP 7.0 and earlier releases. It is recommended to use the primary wildfly-ejb-client-bom if possible.
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.
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.
This artifact provides a bill of materials (BOM) for remoting based EJB for clients
which require 100% API compatiblity with EAP 7.0 and earlier releases. It is recommended
to use the primary wildfly-ejb-client bom if possible.
Apache Geode provides a database-like consistency model, reliable transaction processing and a shared-nothing architecture to maintain very low latency performance with high concurrency processing
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.
This artifact provides a bill of materials (BOM) for remoting based EJB for clients
which require 100% API compatiblity with EAP 7.0 and earlier releases. It is recommended
to use the primary wildfly-ejb-client bom if possible.
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.