GitLab

Benedikt Kleinmeier authored Jul 11, 2019 and Daniel Lehmberg committed Jul 11, 2019

This new class is used by:

  - VadereApplication
  - VadereConsole
  - PostVisualization

Now, all Vadere applications have a unified interface to pass arguments on command line.

Watch out: The method "VadereConsole.addSubCommandsToParser()" should be moved to "VadereArgumentParser".

Moved configuration of Maven's code coverage plugin "JaCoCo" from subprojects to top-level "pom.xml".

refactoring of the module / package structure: potentialfield calculators are now in the module simulation and the module meshing requires the module utils which is again the module without dependencies. simulation depends on meshing

Moved CI helper scripts to "Tools/ContinuousIntegration" and enabled Java assertions in POM files and helper scripts.

.gitlab-ci.yml:
- Refactored complete file: moved comment on top of file.
- Call helper scripts in "Tools/ContinuousIntegration" instead of just "Tools".

Tools/ContinuousIntegration/run_vadere_console_with_all_scenario_files.py:
- Execute scenario files alphabetically.
- Use "-enableassertions" when invoking Java.

POM files:
- Use "<enableAssertions>true</enableAssertions>" to be independent of SureFire's default settings.

In "pom.xml" files, added "failIfNoTests" to avoid that module is (wrongly) marked as error if no tests were executed.

Otherwise, a module is flagged as error if no unit tests were executed at all.

In "pom.xml" of "VadereGui", "VadereSimultor", "VadereState" and "VadereUtils", use version 2.19 of Surefire plugin to be able to skip tests via CLI.

Version 2.19 or higher of Surefire plugin allows to use following notation to skip tests:

  mvn test -Dtest=!LegacyTest

Note: maybe, use "mvn test -Dtest=\!LegacyTest" (with escape character) to avoid shell interpretation of exlemation mark.

Extended "pom.xml" to generate coverage reports in CSV, HTML and XML by using "jacoco-maven-plugin".

Generate reports by executing:

  mvn test

Generated reports are located in:

  <project_root>/target/site/coverage-reports

Now, this Maven config can be used to activate report generation in Gitlab.