Given recent class-loading bugs (such as CPS-1933 and CPS-1866), after investigation it was discovered that the Spring Boot executable JAR being produced for cps-application is causing these issues.

This story is to get agreement between team and stakeholders as to what artifacts should be delivered (e.g. thin JAR, maven shade JAR, etc.)
The details of the agreement should also be recorded on a Wiki only available to EST and Ericsson employees e.g child page of https://eteamspace.ericsson.net/pages/viewpage.action?spaceKey=RERIC&title=Team+CPS

A/C

1. Maven-built JAR artifacts within cps repos must each possess a version number that is unique and not just SNAPSHOT version.
2. All JAR artifacts must be stored in a publicly accessible repository, such as ONAP or Nordix Nexus repositories.
3. Third-party transitive dependencies,->Spring Boot, should be retrievable from Maven Central.
4. ONAP dependencies, including oparent, must be available in the same public repository as cps.
5. All dependencies, including cps, oparent, and third-party dependencies, must undergo the generic FOSS procedure for approval.
6. The FOSS approval process must be successfully completed for all dependencies before proceeding with the transfer of binaries - Are we then dependent on Ericsson for this ?
7. Approved artifacts, will be accessible to the eric-oss-ncmp build pipeline for integration into the software build process.

These acceptance criteria ensure compliance with versioning standards, repository accessibility, FOSS approval procedures, and integration into Ericsson's build pipeline for the eric-oss-ncmp project.