Skip to content

GitLab

Closed
Created by Benedikt Kleinmeier@hm-kleinmeiMaintainer

Option "--logname" for "vadere-console.jar" is broken after updating to log4j2

Summary

When migrating to log4j version 2, Stefan just commented out essential code in class SetLogNameCommand. Since then, the option --logname <filename> is ignored by vadere-console.jar.

What is the current bug behavior?

No log file is created as specified with --logname <filename>.

Steps to reproduce

  1. git checkout master
  2. mvn -Dmaven.test.skip=true package
  3. java -jar VadereSimulator/target/vadere-console.jar --logname test.log scenario-run -f VadereModelTests/TestOSM/scenarios/basic_2_density_discrete_ca.scenario

Relevant data

  • [If you report a bug] Git branch name and commit hash: master

Starting point

  • Class SetLogNameCommand.java already contains a "FIXME" comment.

The class should create a FileAppender programmatically and should add it to the root logger.

To upload designs, you'll need to enable LFS and have an admin enable hashed storage. More information