commit | 7d81ee081cdd92a298c4fa7314c5ea3606167efa | [log] [tgz] |
---|---|---|
author | nadeeshani.jayathilake <nadeeshani.jayathilake@est.tech> | Wed Nov 23 10:05:54 2022 +0000 |
committer | nadeeshani.jayathilake <nadeeshani.jayathilake@est.tech> | Mon Nov 28 10:56:38 2022 +0000 |
tree | 925d297a947bdf1b45913643bfb006fdee6c280d | |
parent | 26714e691a2077a5e190b3da3e0824321a7429a1 [diff] |
Clean up Helm Charts Downloaded Directories Issue-ID: SO-4031 Signed-off-by: nadeeshani.jayathilake <nadeeshani.jayathilake@est.tech> Change-Id: I5c8e8ca9812779076d295ae6b0bbc78d766ee0f3
SO CNFM project which handles the AS/CNF Lifecycle Management.
SO CNFM can be compiled with mvn clean install
Subscribe and post messages with SO tag in onap-discuss group at https://lists.onap.org/g/onap-discuss
SO-CNFM is composed of a main pom.xml which is structured to build packages (docker image preparation file) and so-cnfm-lcm modules. Also, so-cnfm-lcm is structured to build all submodules and there is individual pom.xml for each submodule. so-cnfm-lcm is composed of so-cnfm-lcm-api – generates the POJOs for REST APIs. so-cnfm-lcm-application – creates Spring Boot application jar file. so-cnfm-lcm-bpmn-flows - Camunda BPM engine code flow for step-by-step order flow execution. so-cnfm-lcm-database-service – mariadb for storing metadata. so-cnfm-lcm-service – contains the REST APIs.