AT:

• processes.xml is not used any more for process application configuring
• instead process application is configured via Spring properties within camunda.bpm.application
• we warn in log if processes.xml is still present in its common location (it is ignored!)
• limitations are documented

Hint:
extend RuntimeContainerDelegateImpl and replace the deployment operation step ParseProcessesXmlStep with the one reading from Spring properties

Also see this issue: https://github.com/camunda/camunda-bpm-spring-boot-starter/issues/77