Open ThorbenLindhauer opened 4 years ago
This comment was imported from JIRA and written by user @yanavasileva
Doc of resourceRootPath
: https://docs.camunda.org/manual/7.13/reference/deployment-descriptors/tags/process-archive/
local to the root of the classpath. By default or if the prefix classpath: is used, the path is interpreted as relative to the root of the classloader. Example: path/to/my/processes or classpath:path/to/my/processes) Doc of spring boot PA: https://docs.camunda.org/manual/7.13/user-guide/spring-boot-integration/process-applications/
Workarounds:
BOOT-INF/classes/bpmn
in that case will work for running the application as jar but will fail if it's started via IDE.deployment-resource-pattern
Root cause: Repackaging during the build, details will follow.
This issue was imported from JIRA:
Steps to reproduce
src/main/resources/bpmn
folderPlaced following entry in
processes.xml
2020-07-07 15:17:05.613 INFO 2024 --- < main> org.camunda.bpm.container : ENGINE-08024 Found processes.xml file at jar:file:/Users/garima.yadav/eclipse-workspace/sampleproject3/target/sampleproject3.jar!/META-INF/processes.xml 2020-07-07 15:17:05.702 INFO 2024 --- < main> org.camunda.bpm.container : ENGINE-08021 Not creating a deployment for process archive 'camundaApplication': no resources provided. 2020-07-07 15:17:05.707 INFO 2024 --- < main> org.camunda.bpm.container : ENGINE-08050 Process application camundaApplication successfully deployed