Build jar #4
Build jar #4
Conversation
There was a problem hiding this comment.
The JAR artifact built in the CI and when running it via the container both work (the JAR contains the necessary dependency classes and only fails in the sending step when setting some dummy ENV-vars).
The release artifact upload looks like the one for Artemis, so that should work, too.
So, only one small question about the local vs. CI build, looks good otherwise. 👍
| RUN gradle clean classes | ||
| RUN gradle clean jar | ||
|
|
||
| FROM eclipse-temurin:8-jre |
There was a problem hiding this comment.
Just a question out of curiosity, fine as-is: Is there are reason why JDK 8 is used instead of, e.g. LTS17? As the JAR is only running inside a Docker container there should be no environment constraints.
There was a problem hiding this comment.
For parsing the XML files we need some dependencies (JAXB). I remember that when I initialized this plugin it was complicated to find the right dependencies as they were handled by a corresponding Jenkins dependency.
Therefore, I just used this version to make it working, but it is planned to update the Java version.
Co-authored-by: Benedikt Fein <fein@fim.uni-passau.de>
Fixes #2
In this PR, we add the gradle task to build a jar. The build result will be added to a new release.
The jar is used in the Docker image. Therefore, it is sufficient to have only java installed.
TODO: When this PR is merged, it is necessary to adapt the command for using the plugin in Artemis (together when updating the version):