Camunda Migration
Migrating an existing application from Camunda 7.22 to CIB seven 1.0 is straightforward. This page describes the necessary steps.
Migration to CIB seven 1.0
CIB seven 1.0 is a special version with minimal changes from Camunda. No source level changes were applied, no library dependencies were changed.
We expect migration to this version should be as easy as possible. Only two steps are essential:
Change Version to 7.22.0-cibseven
My Camunda version is less than 7.22!
For Camunda versions before 7.22 please do minor updates before migrating to CIB seven as described in Camunda version upgrade docs.
Update your pom.xml
files using Camunda and change version used from 7.22.x
(usually 7.22.0
for Community Edition) to 7.22.0-cibseven
.
Setup CIB seven Maven Repository
We are not able to deliver artifacts for other projects to any Maven Central repository. Version 7.22.0-cibseven
is available only at artifacts.cibseven.org - our public maven repository.
You can add this repository to pom.xml
for current project or to settings.xml
in $M2_HOME
(usually $HOME/.m2
) folder for current user:
<repositories>
<repository>
<id>mvn-cibseven-public</id>
<name>CIB seven Public Repository</name>
<url>https://artifacts.cibseven.org/repository/public/</url>
</repository>
</repositories>
Migration to CIB seven 1.1
Don't panic and use OpenRewrite!
There are renamings done in this version. It is too boring to do it manually. Just use Migration Script we made for you!
CIB seven 1.1 has set of changes for versions, packages and artifacts naming. So you will need to update:
- Versions used (in
pom.xml
files):7.22.0
->1.1.0
. - Artifacts names are changes from
camunda-*
tocibseven-*
(for examplecamunda-bpm-spring-boot-starter-webapp
is called nowcibseven-bpm-spring-boot-starter-webapp
). - Imports used in custom code should now use
org.cibseven.foo.bar
instead oforg.camunda.foo.bar
packages.
All these changes can be done, using our Migration Script, based on OpenRewrite maven plugin (see GitHub for details).