...
| Path | Content |
|---|---|
| Docs | |
| /docs | The documentation in .rst files |
| Docker | |
| /extra/docker/clamp | The docker compose file to start clamp and the Mariadb |
| /extra/docker/mariadb | The mariadb conf files used by docker compose |
| /extra/sql | The SQL file containing the CLAMP schema, Clamp Stored procedures and Camunda schema |
| /src/main/docker | The Docker file + the scripts to start clamp that are used to build the image |
| Code | |
| /src/main/java | The back-end and front-end code + resources |
| /src/main/test | The unit tests and Spring integration tests to validate CLAMP code |
| /src/main/scripts | Groovy scripts used by maven build |
| /src/main/resources | The default CLAMP configuration files + the Front end code |
| /src/main/resources/bpmn | The bpmn files used by camunda engine |
| /src/main/resources/clds | The Clamp specific configuration files |
| /src/main/resources/xsl | The xsl used to convert BMPN XML to JSON (from designer UI) |
| /src/main/resources/META-INF/resources | The front end code |
| /src/main/resources/META-INF/resources/designer | The designer front code (HTML + javascript) |
Building CLAMP
To build CLAMP you need to use maven with the goal "clean install". By default it executes the standard unit tests and the Spring integration tests but does not build the docker images.
You can disable the integration tests by executing: "mvn clean install -DskipITs=true"
There are one profile to build the docker image named "docker", to build the docker image: "mvn clean install -P docker"
Testing CLAMP
We created CSIT (Continuous System and Integration Testing) tests for clamp as requested for each ONAP component. This use Robot Framework. See this wiki page for more information: Creating a CSIT Test
...