...
We have seen how the pom.xml file create creates the ~/ccsdk/distribution/odlsli/target/docker-stage directory in preparation for building the docker image. The next step is to inspect the Dockerfile that creates the image, discussed here.
...
Yet another aspect for the context of the installer is that CCSDK changed the procedure to install karaf features from Beijing to Casablanca, but some elements of the prior procedure are still present. Prior to Casablanca, all of the CCSDK features were copied into a directory in the ccsdk home directory '/opt/onap/ccsdk/features/,' and the entry point script in the Docker container would install them. The contents of the ccsdk home directory and features directory for Beijing are shown here.
As we can see, there each feature is in a directory with the name "ccsdk-<feature-name>," and the directory contains a zip file with the name "ccsdk-<feature-name>-<version>.zip" and an 'install-feature.sh' script for each feature. The zip file is simply the maven repository for the feature, as shown here for ccsdk-sliapi.
...
And here is the 'install-feature.sh' script.
Inspecting the installer pom.xml file
Below is the annotated pom.xml file. It executes two maven phases: prepare-package and package. Although Maven executes the prepare-package phase before the package phase, although, in the pom.xml file, the prepare-package code appears after the prepare code in the pom.xml file. In the annotations, the sequence is indicated by number.
...