Include Java Binaries in the Nightly Build
The AF3 build shall be "portable", i.e., no longer require users to install the correct Java version on their system. ## Implementation It might be sufficient to unzip the correct Java binaries in a `jre/` folder in the AF3 root directory. This is where the binaries are looked for first. No other file changes should be necessary. ## Deployment The bundling shall be done in the `deploy` step. Here, the ZIP files built by Maven shall be unzipped, modified, and zipped again. ## Licensing The classpath exception of Java's GNU GPL licence should allow bundling. ## Testing 1. Run the "Bundled Build" pipeline (see https://git.fortiss.org/af3/maven-releng/-/pipeline_schedules). This pipeline is set up to build the 4357 branch (this must be changed to `master` once the branch is merged) with the `JRE_TYPE` variable set accordingly. As it is "inactive", it only runs when executed manually: ![grafik](/uploads/2184383697f943a939aa8944195ab3fe/grafik.png) 2. Download the pipeline's artifacts. The resulting build shall be tested on Windows and Linux systems with (1) no Java installation, (2) an incompatible Java installation, and (3) the correct Java installation.
issue