Details
-
Feature Request
-
Resolution: Unresolved
-
L3 - Default
-
None
-
spring-boot 3.3.5
Description
Spring Boot, through the spring-boot-maven-plugin and spring-boot-gradle-plugin generates executable jars, which are repackaged from the original one by changing its folder structure and adding a BOOT-INF/classes nested directory between the root classpath level and the jars resources.
When deploying Process Archives with processes.xml, this nested directory breaks the assumption that the resources are located at one of the following places:
- On the root classpath level;
- On the same level as META-INF/ (where processes.xml is stored).
This causes multi-tenancy deployments to not be supported in certain cases (ex. when executing the executable jar with java -jar).
Project to reproduce: https://github.com/ThorbenLindhauer/camunda-example-tenant-specific-dmn