Merge branch '1-mavenize-and-add-test' into 'master'

Resolve "mavenize and add test"

Closes #1

See merge request !1

README.md

@@ -2,11 +2,11 @@
 
 ## prerequisites:
 
-* use a proper java IDE - eclipse/intellij/netbeans for example https://www.eclipse.org/downloads/
-* use explicitly plain java or an established java framework (spring, play etc.)
-* use an established json library (for example jackson) - https://github.com/FasterXML/jackson-databind
-* use maven - https://maven.apache.org/
-* use git - https://git-scm.com/
+* use java. So please download a JDK. For example from https://www.azul.com/downloads/?package=jdk 
+* install and use a proper java IDE - eclipse/intellij/netbeans for example https://www.eclipse.org/downloads/
+* install and use an established json library (for example jackson) - https://github.com/FasterXML/jackson-databind
+* install and use maven - https://maven.apache.org/
+* if you have an account at mygit.th-deg.de then please use git - https://git-scm.com/
 
 ## 1. Task description in short:
 
@@ -19,8 +19,8 @@
 ## 2. Task description in detail:
 
 Please keep in mind! Others are working on the same repository!  
-So you have various ways of committing code without conflicting with their work. The best practice here would be a
-fork:  
+So you have various ways of committing code without conflicting with their work.
+If you have an account at mygit.th-deg.de the best practice here would be a fork:  
 See as example:  
 https://docs.gitlab.com/ee/user/project/repository/forking_workflow.html
 
@@ -28,6 +28,8 @@ https://docs.gitlab.com/ee/user/project/repository/forking_workflow.html
 Don´t push code to the master branch. Use your own branch or fork!
 So we can evaluate all applicants separately.**
 
+If you do not have an account, please **clone** this repository, work on it locally, and send us your solution (e.g. via mail or via dropbox etc).
+
 ## 3. Tests:
 
 Make sure all maven tests run successfully when doing `mvn clean test` for example on a terminal