Skip to content
GitLab
Menu
Projects
Groups
Snippets
Help
Help
Support
Community forum
Keyboard shortcuts
?
Submit feedback
Contribute to GitLab
Sign in
Toggle navigation
Menu
Open sidebar
Thomas Lang
jsonparser
Commits
d9e4ab3f
Commit
d9e4ab3f
authored
Jul 13, 2021
by
Thomas Lang
Browse files
Merge branch '1-mavenize-and-add-test' into 'master'
Resolve "mavenize and add test" Closes
#1
See merge request
!1
parents
7d35573d
9afb3ad6
Changes
1
Hide whitespace changes
Inline
Side-by-side
README.md
View file @
d9e4ab3f
...
...
@@ -2,11 +2,11 @@
## prerequisites:
*
use
a proper java IDE - eclipse/intellij/netbeans f
or 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. F
or 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
...
...
Write
Preview
Markdown
is supported
0%
Try again
or
attach a new file
.
Attach a file
Cancel
You are about to add
0
people
to the discussion. Proceed with caution.
Finish editing this message first!
Cancel
Please
register
or
sign in
to comment