Today, in some cases, the kieserver-pull.sh script is pulling artifacts twice, during the s2i build and during the image startup.

This should be one single process and the local m2 repository should contain everything that is needed.

Chatting with David, he figured out that a few more goals can be added to help to prevent this behavior to happen:

mvn -e \
    dependency:resolve \
    dependency:resolve-plugins \
    dependency:go-offline \
    clean \
    compile \
    test \
    package \
    -f pom.xml \
    -s ~/.m2/settings.xml \
    --batch-mode \
    -Dcheckstyle.skip=true \
    -Dfabric8.skip=true \
    -Dfindbugs.skip=true \
    -DincludeScope=test \
    -Djacoco.skip=true \
    -Dmaven.javadoc.skip=true \
    -Dmaven.site.skip=true \
    -Dmaven.source.skip=true \
    -Dpmd.skip=true

On kieserver-pull.sh we only used dependency:go-offline, but those other dependency:* goals plus the includeScope=test are the key differences.