migrate-from-camunda-recipe

KO | EN

gitlite — search

#javascript #typescript #go #golang #android #deep-learning #nodejs #awesome #cli #kubernetes #vue #awesome-list #security #mcp

migrate-from-camunda-recipe

(★ 14)

An Open Rewrite Recipe to migrate a Camunda 7 Instance to Operaton

migrate-from-camunda-recipe Latest Version Download

Download Latest Version (.zip)

// repository documentation

Was this content helpful?

★ 0 (0 ratings)

# Migrate from Camunda to Operaton Recipes

This repository contains [OpenRewrite](https://docs.openrewrite.org/) recipes to help migrate your applications from [Camunda 7](https://docs.camunda.org/manual/7.24) to Operaton.

## Available Recipes

The following recipes are available to assist with migration:

### MigrateFromCamunda

**MigrateFromCamunda** - A meta recipe that applies all the necessary migration steps to move a Camunda 7 project to Operaton (aggregates dependency, API, type/package, constants/methods, and descriptor migrations).

1. **ReplaceCamundaDependencies** - Replaces Camunda Maven dependencies with their Operaton equivalents.
1. **ChangeMethod** - Replaces calls/overrides of Camunda methods with their Operaton equivalents when method names are containing substring `Camunda`.<br />(e.g., `getCamundaExpression()` -> `getOperatonExpression()`)
1. **ChangeConstant** - Replaces usage of Camunda constants with their Operaton equivalents when constant names
   are containing substring `Camunda`.<br />(e.g., `org.camunda.bpm.engine.authorization.Groups.CAMUNDA_ADMIN` -> `org.operaton.bpm.engine.authorization.Groups.OPERATON_ADMIN`)
1. **ChangeType** - Replaces usages of Camunda types with their Operaton equivalents when simple class names changed (e.g., `CamundaX` -> `OperatonX`). Complements ChangePackage.
1. **ChangePackage** - Renames selected Camunda Java packages to their Operaton counterparts.
1. **MigrateDeploymentDescriptors** - Updates XML namespace declarations in deployment descriptor files.
1. **RenameServiceLoader**: Rename selected ServiceLoader files in META-INF/services.
1. **ResolveDeprecations** - Resolves deprecated API usages.

### MigrateSpringBootApplication
A meta recipe that applies the generic recipes and all necessary migration steps to migrate a Spring Boot application from Camunda to Operaton.

```xml
<activeRecipes>
    <recipe>org.operaton.rewrite.spring.MigrateSpringBootApplication</recipe>
</activeRecipes>
```

### MigrateQuarkusApplication
A meta recipe that applies the generic recipes and all necessary migration steps to migrate a Quarkus application from Camunda to Operaton.

```xml
<activeRecipes>
    <recipe>org.operaton.rewrite.quarkus.MigrateQuarkusApplication</recipe>
</activeRecipes>
```

## Known Issues

### RenameServiceLoader

When a service loader file which is renamed, contains a class which is relocated (rename-package, or rename-types) from camunda to operaton, the file itself is renamed but the content (the class to be loaded) is not. Please check the output of the rewrite run:

```text
[WARNING]     org.operaton.rewrite.RenameServiceLoader
[WARNING]         org.openrewrite.RenameFile: {fileMatcher=**/META-INF/services/org.camunda.spin.spi.DataFormatProvider, fileName=org.operaton.spin.spi.DataFormatProvider}
```
If service loader files have been renamed check their contents and make sure the classes loaded are available.

## How to Use in a Maven Project

To use these recipes in your Maven-based Spring Boot project, add the following to your `pom.xml`:

```xml
<build>
    <plugins>
        <plugin>
            <groupId>org.openrewrite.maven</groupId>
            <artifactId>rewrite-maven-plugin</artifactId>
            <version>6.28.1</version>
            <configuration>
                <activeRecipes>
                    <recipe>org.operaton.rewrite.MigrateFromCamunda</recipe>
                </activeRecipes>
            </configuration>
            <dependencies>
                <dependency>
                    <groupId>org.operaton</groupId>
                    <artifactId>migrate-camunda-recipe</artifactId>
                    <version>1.0.1</version>
                </dependency>
            </dependencies>
        </plugin>
    </plugins>
</build>
```

Then run:

```bash
mvn rewrite:run
```

## How to Use in a Gradle Project

For Gradle projects, add the following to your `build.gradle`:

```groovy
plugins {
    id("java")
    id("org.openrewrite.rewrite") version("7.25.0")
}

repositories {
    // Include mavenLocal so recipe SNAPSHOTs published locally can be resolved
    mavenLocal()
    mavenCentral()
}

dependencies {
    rewrite("org.operaton:migrate-camunda-recipe:1.0.1")
}

rewrite {
    activeRecipe("org.operaton.rewrite.MigrateFromCamunda")
}
```

Then run:

```bash
./gradlew rewriteRun
```

## Using Individual Recipes

If you want to apply only specific recipes, you can specify them individually:

```xml
<activeRecipes>
    <recipe>org.operaton.rewrite.ChangePackage</recipe>
    <recipe>org.operaton.rewrite.ReplaceCamundaDependencies</recipe>
</activeRecipes>
```

Or in Gradle:

```groovy
rewrite {
    activeRecipe("org.operaton.rewrite.ChangePackage")
    activeRecipe("org.operaton.rewrite.ReplaceCamundaDependencies")
}
```

## Running Without Modifying the Build

You can also run the MigrateFromCamunda meta recipe without modifying your build files by using the Maven or Gradle command line:

### Maven

```bash
mvn org.openrewrite.maven:rewrite-maven-plugin:6.28.1:run \
  -Drewrite.recipeArtifactCoordinates=org.operaton:migrate-camunda-recipe:1.0.1 \
  -Drewrite.activeRecipes=org.operaton.rewrite.MigrateFromCamunda
```

### Gradle

[Create a init.gradle file](https://docs.openrewrite.org/running-recipes/running-rewrite-on-a-gradle-project-without-modifying-the-build). It does not need to be in the project directory itself (although it will make it easier for this guide). Copy the below init script to your file:

```groovy
initscript {
  repositories {
    maven { url "https://plugins.gradle.org/m2" }
  }
  dependencies {
    classpath("org.openrewrite:plugin:7.25.0")
  }
}

rootProject {
  plugins.apply(org.openrewrite.gradle.RewritePlugin)
  dependencies {
    rewrite("org.operaton:migrate-camunda-recipe:1.0.1")
  }

afterEvaluate {
    // Include mavenLocal so recipe SNAPSHOTs published locally can be resolved
    if (repositories.isEmpty()) {
      repositories {
        mavenLocal()
        mavenCentral()
      }
    } else {
      repositories {
        mavenLocal()
      }
    }
  }
}
```

```bash
./gradlew --init-script init.gradle rewriteRun -Drewrite.activeRecipe=org.operaton.rewrite.MigrateFromCamunda
```

This approach allows you to apply the migration without adding the plugin to your build configuration.

## Mapping Documentation

For more details on the specific changes made by these recipes, see the [Camunda to Operaton Artifact Mapping](camunda-to-operaton-mapping.md) document.

migrate-from-camunda-recipe

migrate-from-camunda-recipe Latest Version Download

Today's picks

Was this content helpful?

Recent Feedback

migrate-from-camunda-recipe

migrate-from-camunda-recipe Latest Version Download

Today's picks

Was this content helpful?

Recent Feedback

Download README