The Activiti SDK based on Apache Maven, includes support for rapid and standard development, testing, packaging, versioning and release of your Activiti integration and extension projects
We have to find a way to prevent the packaging process of the Activiti Admin for both the WAR and the Docker container.
Typically you need to build the Activiti Admin just for the first time and then we can consider the same build valid for any new Docker run.
If we need to declare Spring annotations for implementing Java delegates that we want to use as delegate expressions, we don't have the availability of the Spring Context classes in the classpath.
We need to share the default Java packages enabled in Spring for the ComponentScan.
In this way any developer can put his own Spring Beans annotated with @service or @component without declaring a configuration class.
For the current version of Activiti currently included in the bundle we have the following default extensions points:
org.activiti.app.extension.conf: custom configuration classes for Activiti App
org.activiti.app.extension.bean: custom Spring beans (delegates etc.) for Activiti App
org.activiti.rest.conf: custom Spring beans (delegates etc.) for Activiti Rest
classpath:activiti-custom-context.xml: custom Spring context for Activiti Rest