|
|
|
|
The extension is published on maven central, so if you are using maven, just add the dependency:
<dependency>
<groupId>org.camunda.bpm.extension.springboot</groupId>
<artifactId>camunda-bpm-spring-boot-starter([-rest|-webapp])</artifactId>
<version>2.0.0</version>
</dependency>or use the BOM:
<dependencyManagement>
<dependencies>
<dependency>
<groupId>org.camunda.bpm.extension.springboot</groupId>
<artifactId>camunda-bpm-spring-boot-starter-bom</artifactId>
<version>2.0.0</version>
<type>pom</type>
<scope>import</scope>
</dependency>
</dependencies>
</dependencyManagement>
...
<dependency>
<groupId>org.camunda.bpm.extension.springboot</groupId>
<artifactId>camunda-bpm-spring-boot-starter([-rest|-webapp])</artifactId>
</dependency>and then create a simple process application like this one:
@SpringBootApplication
@EnableProcessApplication
public class WebappExampleProcessApplication {
public static void main(String... args) {
SpringApplication.run(WebappExampleProcessApplication.class, args);
}
}Check out the Documentation and the Examples
-
Issue Tracker - if you have an idea for a new feature or want to file a bug … this is the place to go.
-
Contributing - check this if you want to contribute
-
Discussion Forum - this extension has it’s own sub-category at the camunda forum … use it!
|
Important
|
We have decided to refactor the configuration mechanism. Especially we removed the org.camunda.bpm.spring.boot.starter.configuration.CamundaConfiguration interface. For now each configuration is a org.camunda.bpm.engine.impl.cfg.ProcessEnginePlugin. With this it is possible to hook into preInit, postInit and postProcessEngineBuild which supports more complex situations.
If you have implemented an CamundaConfiguration you have to switch to ProcessEnginePlugin (and its preInit method). You can also extend your configuration from org.camunda.bpm.spring.boot.starter.configuration.impl.AbstractCamundaConfiguration to avoid a cast to SpringProcessEngineConfiguration.
|