RESTEasy client module for consuming RESTful services using the JAX-RS client API.
📦 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.
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.
The Apache Software Foundation provides support for the Apache community of open-source software projects.
The Apache projects are characterized by a collaborative, consensus based development process, an open and
pragmatic software license, ...
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
This is a Bill of Materials (BOM) for internal dependencies of Operaton.
All modules should import this BOM to ensure consistent versions of 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
Bill of Materials for Quatrion Portal — import this BOM to align all quatrion-portal-* versions and inherit Quarkus BOM constraints in a single declaration.
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
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.
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.
Webapp Watcher (WAW) is a Java EE Filter which alows you to log the requests response times and Java stack traces of a Java EE web application (.war). You can later compute usage statistics of the web application, and also track down potential bugs ...
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
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
Quarkus 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 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 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.
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 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.