Edit the Dockerfile to use a jar and multi stage build.
Description
rewriting the Dockerfile to build the standalone jar in a maven container before running it in a openjdk slim container
First packaging the jar using the cli-standalone profile in a maven container
then copying it to a lightweight and clean image to run it
use absolute path to run the jar in the Docker entrypoint
Motivation and Context
It allows to avoid issue when the docker runtime is using a different workdir by default (which cause the mvn java:exec to fail)
Allows to run it using:
On CWL
The 2 first commands are to create the workspace directories (on Ubuntu). The last command is to run the workflow from the root of the GitHub repository https://github.com/MaastrichtU-IDS/d2s-cwl-workflows (after cloning it)
Coverage remained the same at 54.365% when pulling b38d524c1e516a7c52a2eb4f8c1b2a58b3a0e161 on vemonet:develop into c8ae88a206160ef5d61ac01652ab70b8cbbadb9b on AKSW:master.
Edit the Dockerfile to use a jar and multi stage build.
Description
Motivation and Context
It allows to avoid issue when the docker runtime is using a different workdir by default (which cause the mvn java:exec to fail) Allows to run it using:
Issue: https://github.com/AKSW/RDFUnit/issues/98
How Has This Been Tested?
Tested on Ubuntu 18.04. Part of a workflow containing other components:
On Kubernetes
bin/rdfunit
On CWL The 2 first commands are to create the workspace directories (on Ubuntu). The last command is to run the workflow from the root of the GitHub repository https://github.com/MaastrichtU-IDS/d2s-cwl-workflows (after cloning it)
Screenshots (if appropriate):
Types of changes
Checklist: