From e61d48c9c817083de466a67b3775f270a3733a54 Mon Sep 17 00:00:00 2001 From: Torgeir L Date: Wed, 7 Jun 2023 07:10:13 +0200 Subject: [PATCH] update dead link to the new file `log4j2.xml` was replaced by `log4j2-spring.xml` in #3951 --- .../main/resources/META-INF/asciidoc/admin-guide/logging.adoc | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/inception/inception-doc/src/main/resources/META-INF/asciidoc/admin-guide/logging.adoc b/inception/inception-doc/src/main/resources/META-INF/asciidoc/admin-guide/logging.adoc index e81f1f2a4d7..c0cef03991f 100644 --- a/inception/inception-doc/src/main/resources/META-INF/asciidoc/admin-guide/logging.adoc +++ b/inception/inception-doc/src/main/resources/META-INF/asciidoc/admin-guide/logging.adoc @@ -40,7 +40,7 @@ logging.level.de.tudarmstadt.ukp.inception.security=TRACE A custom logging configuration can be specified when starting up {product-name} using the parameter `-Dlogging.config=/path/to/your/log4.xml`. This should be a standard Log4J2 configuration file. -A good starting point is the default configuration used by {product-name} which can be found in link:https://github.com/inception-project/inception/blob/main/inception/inception-app-webapp/src/main/resources/log4j2.xml[our code repository]. +A good starting point is the default configuration used by {product-name} which can be found in link:https://github.com/inception-project/inception/blob/main/inception/inception-app-webapp/src/main/resources/log4j2-spring.xml[our code repository]. == Logging in JSON format