This page lists the most commonly used Apache Maven Coordinates for Camunda.

Most Camunda artifacts are pushed to maven central.

Camunda BOM (Bill of Materials)

Community Edition

<dependencyManagement>
  <dependencies>
    <dependency>
      <groupId>org.camunda.bpm</groupId>
      <artifactId>camunda-bom</artifactId>
      <version>7.22.0</version>
      <scope>import</scope>
      <type>pom</type>
    </dependency>
  </dependencies>
</dependencyManagement>

Enterprise Edition

To use the Enterprise Edition dependencies, you have to add the Enterprise Edition Maven Repository to your project.

<dependencyManagement>
  <dependencies>
    <dependency>
      <groupId>org.camunda.bpm</groupId>
      <artifactId>camunda-bom</artifactId>
      <version>7.22.0-ee</version>
      <scope>import</scope>
      <type>pom</type>
    </dependency>
  </dependencies>
</dependencyManagement>

Camunda Engine

<dependency>
  <groupId>org.camunda.bpm</groupId>
  <artifactId>camunda-engine</artifactId>
</dependency>

Camunda Engine Spring Integration

The camunda-engine Spring integration for Spring Framework 5:

<dependency>
  <groupId>org.camunda.bpm</groupId>
  <artifactId>camunda-engine-spring</artifactId>
</dependency>

The camunda-engine Spring integration for Spring Framework 6:

<dependency>
  <groupId>org.camunda.bpm</groupId>
  <artifactId>camunda-engine-spring-6</artifactId>
</dependency>

Camunda Engine CDI Integration

<dependency>
  <groupId>org.camunda.bpm</groupId>
  <artifactId>camunda-engine-cdi</artifactId>
</dependency>

Camunda DMN Engine BOM (Bill of Materials)

This BOM allows to use the DMN engine standalone without the BPMN engine and the rest of the Camunda Platform.

<dependencyManagement>
  <dependency>
    <groupId>org.camunda.bpm.dmn</groupId>
    <artifactId>camunda-engine-dmn-bom</artifactId>
    <version>7.22.0</version>
    <type>pom</type>
    <scope>import</scope>
  </dependency>
</dependencyManagement>

Camunda DMN

This dependency allows to use DMN engine standalone without the BPMN engine and the rest of the Camunda Platform. It is not needed when using camunda-engine because that already contains the DMN engine.

<dependency>
  <groupId>org.camunda.bpm.dmn</groupId>
  <artifactId>camunda-engine-dmn</artifactId>
</dependency>

Process Application EJB Client

<dependency>
  <groupId>org.camunda.bpm.javaee</groupId>
  <artifactId>camunda-ejb-client</artifactId>
</dependency>

Camunda Artifact Storage

Artifactory

Camunda relies on JFrog Artifactory to provide Camunda artifacts to users at artifacts.camunda.com. The artifact data is stored in Amazon S3 storage and gets served by artifacts.camunda.com via redirects to AWS S3. Users must be able to connect to both endpoints for artifact retrieval.

Community Edition

<repositories>
  <repository>
    <id>camunda-bpm-nexus</id>
    <name>camunda-bpm-nexus</name>
    <url>
      https://artifacts.camunda.com/artifactory/public/
    </url>
  </repository>
</repositories>

Enterprise Edition

The private URL is a virtual repository, which aggregates a multitude of repositories. Those include customer enterprise artifacts and all public artifacts from public to make builds easier if you need those dependencies.

<repositories>
  <repository>
    <id>camunda-bpm-nexus-ee</id>
    <name>camunda-bpm-nexus</name>
    <url>
      https://artifacts.camunda.com/artifactory/private/
    </url>
  </repository>
</repositories>

Using the Enterprise Edition repository requires credentials in your Maven settings ~/.m2/settings.xml:

  <servers>
    <server>
      <id>camunda-bpm-nexus-ee</id>
      <username>YOUR_USERNAME</username>
      <password>YOUR_PASSWORD</password>
    </server>
  </servers>

Browse Camunda Artifact Storage

In order to browse the Camunda artifacts, here are the links which you can use.

Community Edition

This link helps you to browse the artifacts of Camunda Platform community edition.

https://artifacts.camunda.com/ui/native/camunda-bpm

Enterprise Edition

This link helps you to browse the artifacts of Camunda Platform enterprise edition. The user needs to login before accessing the link.

https://artifacts.camunda.com/ui/native/camunda-bpm-ee

Known issues

cURL artifacts

The files are hosted in AWS S3, therefore, Artifactory rewrites the requests to S3 and sends a 302 as the first response. For cURL this means to add the “-L” or “--location” option to follow the response.

Example:

curl -LO https://artifacts.camunda.com/artifactory/camunda-bpm/org/camunda/bpm/camunda-engine-rest/7.22.0/camunda-engine-rest-7.22.0.war

Other Camunda Modules:

• DMN Engine
• Camunda Spin
• Camunda Connect
• Templating Engines
• Spring Boot Integration