-
Bug Report
-
Resolution: Cannot Reproduce
-
L3 - Default
-
None
-
None
-
None
We support the camunda.bpm.enabled property for quite a while now.
It is supposed to disable the camunda engine setup in (test-)contexts.
However, a colleague just showed me a SpringBootTest that has the property set to false via yaml and fails due to the context error that ProcessEngine can not be injected into the SpringBootProcessApplication
We should verify that this property still works as documented, especially in combination with the "EnableProcessApplication" annotation.
Note: first step would be verification ... I built the property feature myself some while ago and I believed it worked as designed ...