|Nikola Koevski 7d81e9e266||2 months ago|
|.github||3 months ago|
|bom||1 day ago|
|database||1 day ago|
|distro||18 hours ago|
|engine||18 hours ago|
|engine-cdi||1 day ago|
|engine-dmn||1 day ago|
|engine-plugins||1 day ago|
|engine-rest||18 hours ago|
|engine-spring||1 day ago|
|examples/invoice||1 day ago|
|javaee||1 day ago|
|model-api||1 day ago|
|parent||1 day ago|
|qa||18 hours ago|
|settings||1 month ago|
|spring-boot-starter||1 day ago|
|typed-values||1 day ago|
|webapps/h2-webapp||1 day ago|
|.gitignore||3 years ago|
|CONTRIBUTING.md||5 months ago|
|LICENSE||10 months ago|
|NOTICE||1 month ago|
|README.md||2 months ago|
|pom.xml||1 day ago|
camunda BPM platform is a flexible framework for workflow and process automation. It's core is a native BPMN 2.0 process engine that runs inside the Java Virtual Machine. It can be embedded inside any Java application and any Runtime Container. It integrates with Java EE 6 and is a perfect match for the Spring Framework. On top of the process engine, you can choose from a stack of tools for human workflow management, operations & monitoring.
camunda BPM platform provides a rich set of components centered around the BPM lifecycle.
In contrast to other vendor BPM platforms, camunda BPM strives to be highly integrable and embeddable. We seek to deliver a great experience to developers that want to use BPM technology in their projects.
Out of the box, camunda BPM provides infrastructure-level integration with Java EE Application Servers and Servlet Containers.
Most of the components that make up the platform can even be completely embedded inside an application. For instance, you can add the process engine and the REST Api as a library to your application and assemble your custom BPM platform configuration.
camunda BPM is available on maven central but for development of the platform, you have to add our public nexus repository to your maven settings.xml. Add the following lines to it:
<profiles> <profile> <id>camunda-bpm</id> <repositories> <repository> <id>camunda-bpm-nexus</id> <name>camunda-bpm-nexus</name> <releases> <enabled>true</enabled> </releases> <snapshots> <enabled>true</enabled> </snapshots> <url>https://app.camunda.com/nexus/content/groups/public</url> </repository> </repositories> </profile> </profiles> <activeProfiles> <activeProfile>camunda-bpm</activeProfile> </activeProfiles>
Apache Maven 3 and Java JDK 8+ are prerequisites for building camunda BPM platform. Once you have setup Java and Maven, run
mvn clean install
This will build all the modules that make up the camunda BPM platform but will not perform any integration testing. After the build is completed, you will find the distributions under
distro/tomcat/distro/target (Apache Tomcat 9 Distribution) distro/wildfly/distro/target (WildFly AS Distribution)
The integration testsuites are located under
qa/. There you'll find a folder named XX-runtime for
each server runtime we support. These projects are responsible for taking a runtime container
distribution (ie. Apache Tomcat, WildFly AS ...) and configuring it for integration testing. The
actual integration tests are located in the
In order to run the integration tests, first perform a full install build. Then navigate to the
We have different maven profiles for selecting
In order to configure the build, compose the profiles for runtime container, testsuite, database. Example:
mvn clean install -Pengine-integration,wildfly,h2
If you want to test against an XA database, just add the corresponding XA database profile to the mvn cmdline above. Example:
mvn clean install -Pengine-integration,wildfly,postgresql,postgresql-xa
You can select multiple testsuites but only a single database and a single runtime container. This is valid:
mvn clean install -Pengine-integration,webapps-integration,tomcat,postgresql
There is a special profile for the WildFly Application Servers:
mvn clean install -Pengine-integration,h2,wildfly-domain
Due to the fact that the number of unit tests in the camunda engine increases daily and that you might just want to test a certain subset of tests the maven-surefire-plugin is configured in a way that you can include/exclude certain packages in your tests.
There are two properties that can be used for that:
When using the includes only the packages listed will be include and with excludes the other way around. For example calling Maven in the engine directory with
mvn clean test -Dtest.includes=bpmn
will test all packages that contain “bpmn”. This will include e.g.
*api.bpmn*. If you want to limit this further you have to get more concrete. Additionally, you can combine certain packages with a pipe:
mvn clean test -Dtest.includes=bpmn|cmmn
will execute all bpmn and cmmn tests.
The same works for excludes. Also, you can combine both:
mvn clean test -Dtest.includes=bpmn -Dtest.excludes=bpmn.async
Please note that excludes take precedence over includes.
To make it easier for you we created some profiles with predefined in- and excludes:
So simply call
mvn clean test -PtestExceptBpmn
and all the bpmn testcases won't bother you any longer.