-
Type:
Bug Report
-
Resolution: Unresolved
-
Priority:
L3 - Default
-
None
-
Affects Version/s: None
-
Component/s: None
-
None
-
Upgrade
-
4
-
Not defined
Hello Camunda support,
We are going throug upgrade from camunda 7.12.0 to 7.13.8.
We have dependency structure as parent(specify versions in dep.management) – common(specify some logic, preparing beans,etc.) – actual microservices
Before we were specifying all modules of jar we needed separately in parent pom:
<dependency>
<groupId>org.camunda.bpm.springboot</groupId>
<artifactId>camunda-bpm-spring-boot-starter-webapp-ee</artifactId>
<version>${camunda-bpm-spring-boot-starter-webapp.version}</version>
</dependency>
<dependency>
<groupId>org.camunda</groupId>
<artifactId>camunda-bpm-release-parent</artifactId>
<version>${camunda-bpm-spring-boot-starter-webapp.version}</version>
</dependency>
<dependency>
<groupId>org.camunda.bpm.springboot</groupId>
<artifactId>camunda-bpm-spring-boot-starter-rest</artifactId>
<version>${camunda-bpm-spring-boot-starter-webapp.version}</version>
</dependency>
<dependency>
<groupId>org.camunda.bpm.extension</groupId>
<artifactId>camunda-bpm-assert</artifactId>
<version>${camunda-bpm-assert.version}</version>
</dependency>
<dependency>
<groupId>org.camunda.bpm</groupId>
<artifactId>camunda-engine</artifactId>
<version>${camunda-engine.version}</version>
</dependency>
<dependency>
<groupId>org.camunda.bpm.dmn</groupId>
<artifactId>camunda-engine-dmn</artifactId>
<version>${camunda-engine.version}</version>
</dependency>
Now i found it can be done using boms, which should provide correct versions - it is great(maybe it was there before not sure).
<dependency>
<groupId>org.camunda.bpm</groupId>
<artifactId>camunda-bom</artifactId>
<version>${camunda-bom.version}</version>
<scope>import</scope>
<type>pom</type>
</dependency>
<dependency>
<groupId>org.camunda.bpm.dmn</groupId>
<artifactId>camunda-engine-dmn-bom</artifactId>
<version>${camunda-dmn-bom.version}</version>
<type>pom</type>
<scope>import</scope>
</dependency>
Version is 7.13.8-ee
During upgrade i found that we use dependency feel-engine-plugin, but bom does not specify version for it, so we tried 1.10.1, the latest one
<dependency> <groupId>org.camunda.bpm.extension.feel.scala</groupId> <artifactId>feel-engine-plugin</artifactId> <version>1.8.0</version> </dependency>
</dependency>We use this to create configuration for CamundaFeelEnginePlugin, as well as CamundaFeelEngineFactory, etc.
Issue is that when i mix camunda feel-engine with the one going from the plugin we got exception in unit tests : unit-test-exception.txt
Once i exclude plugin from common tests are fine but i cannot start service due to missing FellEngineFactory: exception-without-plugin.txt
I am also adding mvn dependency:tree output on our service that exposes camunda cocpit dependency-tree-with-common.txt
May you please advise how to solve this problem?
Or please specify if you need more information.