...
The "docker" profile defines an additional phase in which the docker image is built and deployed to NEXUS_DOCKER_REPO using with the image name ${image.name}:${project.docker.latesttag.version}, which currently translates to "onap/ccsdk-odlsli-image:0.3-STAGING-latest."
Running the ODLSLI pom.xml file
Running the command "mvn clean process-sources" will create the correct file and folder structure in ./target/docker-stage that one can then use to build the docker image with the command "docker build ." I expect that the "docker build profile" requires special privileges because it deploys the image to NEXUS_DOCKER_REPO.
Creating the zip installation files for karaf features
We now see how the karaf features for OpenDaylight CCSDK are structured so they can be installed and OpenDaylight launched. The next step is to understand how the installation folders in CCSDK_HOME/features zip installation files are created. A good example is the '"sliapi' " feature that is part of the CCSDK_CORE_FEATURES. In the gerrit repository, this code appears in , which is in the gerrit repository ccsdk/sli/core/sliapi.
The sliapi directory contains the usual directories for a karaf feature with an additional directory "installer." This directory contains the code that creates the installation folder stored in the CCSDK_HOME/features folder in the ODLSLI container.
...