The Camunda Community Edition of Camunda is the default version normally built into SO. With the Community Edition, you can see process definitions, but you cannot inspect running or completed process instances, which is an essential debugging capability. This capability is available only in the Enterprise Edition and requires a commercial license. If you have such a license, you can build SO with the Enterprise Edition. Your use must be consistent with the terms of your license, of course.
...
Add a profile to your maven settings.xml to include the repository containing your Camunda EE artifacts.
ExampleFor example:
<profile> <!-- profile for artifacts not in public repositories --> <id>my-local-artifacts</id> <repositories> <repository> <!-- Local repository for Camunda Enterprise Edition --> <!-- YOU MUST HAVE A VALID LICENSE TO USE THIS --> <id>camunda-ee</id> <name>camunda-ee</name> <url>file:///home/john/onap/camunda-ee-repository</url> </repository> </repositories> </profile> </profiles>
And add
...
your profile to the list of active profiles:
...
<activeProfiles>
...
<activeProfile>my-local-artifacts</activeProfile>
...
<activeProfile>openecomp-staging</activeProfile>
...
<activeProfile>openecomp-public</activeProfile>
...
<activeProfile>openecomp-release</activeProfile>
...
<activeProfile>openecomp-snapshots</activeProfile>
...
<activeProfile>opendaylight-release</activeProfile>
...
<activeProfile>opendaylight-snapshots</activeProfile>
...
</activeProfiles>
Building
Add these options to the mvn command line when you build "so"
...