Personalfragebogen 2.0 @ DATEV

1. Clone the project using git clone [email protected]:JOBAA/amos-ss15-proj4.git
2. Change to the project directory using cd amos-ss15-proj4
3. Run ./gradlew idea or ./gradlew eclipse, depending on which IDE you use.
4. Load the project in the IDE using "Import existing (Gradle) Project" or similar.

git clone [email protected]:JOBAA/amos-ss15-proj4.git
cd amos-ss15-proj4
./gradlew idea # For IntelliJ Idea
./gradlew eclipse # For Eclipse

To get a list of available commands, use ./gradlew tasks.

Configuration is held in YAML files. We have a main configuration with application wide configuration. Then, there is a developer specific configuration file which overrides any configuration that a developer might have locally. To enable this, just rename the file:

# Linux
mv src/main/resources/config/application-developer-specific.yml{.sample,}

# Windows
rename-item -path src/main/resources/config/application-developer-specific.yml.sample -newname application-developer-specific.yml

This developer specific configuration file is ignored in our .gitignore and should not be committed to version control, since most probably it contains sensitive information. Further comments on what is loaded in which profile can be found in the file src/main/resources/config/application.yml.

To not confuse the terms Configuration and Profile: a configuration can contain multiple profiles. For example, we could have a configuration use-in-memory-db and a configuration load-sql-from-file-on-startup. These could be combined (and will be resolved hierarchically), as seen in the Spring Boot documentation.

If you want to run the tests using for example ./gradlew test.

We need to have our license at the start of every file. This can be done manually or automatically.

The gradle plugin we use (com.github.hierynomus.license) introduces two tasks:

1. license : Checks for header consistency.
2. licenseFormat : Applies the header (`LICENSE.header`) in files missing it

Yes, there are more than two tasks introduced (6 to be precise). The ones that additionally include the Main or Test part in their name. These however just cover the respective source set and not all source sets. Thus, you most probably do not need them.

Take the license from one of the existing files and copy-paste it over to the new file. Make sure that there is no newline between the license and the package ... part.