Set up github actions

[michellengnx]

• [X] pick a build management environment (i.e Maven or Gradle)
• [X] directory structure to match with this standard directory layout by Apache
• [X] Set up Github Actions on an existing Maven project
• [X] Update maven.yml file with build artifact config

Update Nov 14 2:11 AM: Done. Goodnight, world!

[michellengnx]

and a develop branch too! Update Nov 13: Done

[michellengnx]

Maven and other build management environments (e.g. gradle) are based on the assumption that you do automated testing via e.g. unit tests. For that you need extra code for testing that should not be included in your final product delivered to your customer.

Thus, everything that goes into src/main/java is per default packaged into the product that you would deliver for your customer whereas everything that you put into src/test/java is not.

This is an advantage for various reasons:

• your delivered products are smaller
• it is easier to to find test related code inside your project
• you can load various libraries only for testing.

Stackoverflow reference

[michellengnx]

DONE. Changes merged to develop.

[michellengnx]

Helpful article to set up github actions and docker: https://medium.com/@alexander.volminger/ci-cd-for-java-maven-using-github-actions-d009a7cb4b8f