Maven repository
Published artifacts for org.acemq. No credentials needed.
Four libraries: the AMQP core, its Spring Boot starter, the RabbitMQ management
API, and the load generator.
Maven
<repositories>
<repository>
<id>acemq</id>
<url>https://acemq-company.github.io/maven/</url>
</repository>
</repositories>
<dependency>
<groupId>org.acemq</groupId>
<artifactId>acemq-amqp-core</artifactId>
<version>0.7.15</version>
</dependency>
<dependency>
<groupId>org.acemq</groupId>
<artifactId>acemq-transport-rabbitmq</artifactId>
<version>0.7.15</version>
<scope>runtime</scope>
</dependency>
Gradle
repositories {
mavenCentral()
maven { url = uri("https://acemq-company.github.io/maven/") }
}
dependencies {
implementation("org.acemq:acemq-amqp-core:0.7.15")
runtimeOnly("org.acemq:acemq-transport-rabbitmq:0.7.15")
}
What is published
AceMQ for Java — 0.7.15
Documentation ·
GitHub
| Artifact | What it is |
acemq-amqp-api | The types: Message, Envelope, Publisher, RetryPolicy, Ack |
acemq-amqp-core | The engine: AceMq, publishers, consumers, pipelines, replay |
acemq-transport-spi | The transport contract |
acemq-transport-rabbitmq | RabbitMQ transport — add at runtime |
acemq-amqp-codec-json | JSON, the default format |
acemq-amqp-codec-xml | XML |
acemq-amqp-codec-yaml | YAML |
acemq-amqp-codec-avro | Avro, with a schema registry |
acemq-amqp-codec-protobuf | Protobuf |
acemq-amqp-patterns | Transactional outbox, idempotency stores |
acemq-amqp-test | In-memory broker, for tests without Docker |
acemq-security-api | Pluggable transport security |
Spring Boot starter — 0.7.15
One artifact serves Spring Boot 3 and 4.
Documentation ·
GitHub
| Artifact | What it is |
acemq-spring-boot-starter | The one dependency to add: auto-configuration, the library, the RabbitMQ transport and JSON |
acemq-spring-boot-autoconfigure | The auto-configuration alone, to bring your own transport or codec |
acemq-spring-boot-health-boot3 | Health indicator for Boot 2.7 and 3 |
acemq-spring-boot-health-boot4 | Health indicator for Boot 4 |
<dependency>
<groupId>org.acemq</groupId>
<artifactId>acemq-spring-boot-starter</artifactId>
<version>0.7.15</version>
</dependency>
RabbitMQ Admin — 0.7.15
RabbitMQ's HTTP management API. Its own version line, because it tracks
RabbitMQ rather than AceMQ.
Documentation ·
GitHub
<dependency>
<groupId>org.acemq</groupId>
<artifactId>acemq-java-rabbitmq-admin</artifactId>
<version>0.7.15</version>
</dependency>
Workloads — 0.7.15
A load generator for AMQP brokers. The CLI is a
download on the release
rather than an artifact here — a shaded jar is a download, not a dependency.
Documentation ·
GitHub
<dependency>
<groupId>org.acemq</groupId>
<artifactId>acemq-java-amqp-workloads</artifactId>
<version>0.7.15</version>
</dependency>
Sources and Javadoc jars are published alongside every artifact.
Browse the tree under org/acemq/.
Why not Maven Central
Central is permanent: nothing published there can be removed or altered. That is
the wrong trade before 1.0, while coordinates and API shape are still settling.
Here a bad release can be deleted.
The cost is real and worth knowing before you depend on this. Because these
artifacts are not on Central, any library that depends on AceMQ obliges
its consumers to add this repository too. That is fine for applications
and awkward for libraries. AceMQ moves to Maven Central for 1.0.