This is an automated email from the ASF dual-hosted git repository.
vy pushed a commit to branch doc/perf-main
in repository https://gitbox.apache.org/repos/asf/logging-log4j2.git
commit ee890e0aa6d4e38ec249b23ebcadeb70a9446e70
Author: Volkan Yazıcı <vol...@yazi.ci>
AuthorDate: Wed May 15 10:31:09 2024 +0200
Fix Antora errors
---
.../modules/ROOT/images/whichjar-log4j-1.2-api.png | Bin 0 -> 24992 bytes
.../antora/modules/ROOT/images/whichjar-log4j-api.png | Bin 0 -> 16515 bytes
src/site/antora/modules/ROOT/pages/faq.adoc | 4 ++--
.../pages/{log4j-mongodb4.adoc => log4j-mongodb.adoc} | 0
4 files changed, 2 insertions(+), 2 deletions(-)
diff --git a/src/site/antora/modules/ROOT/images/whichjar-log4j-1.2-api.png
b/src/site/antora/modules/ROOT/images/whichjar-log4j-1.2-api.png
new file mode 100644
index 0000000000..8b54810904
Binary files /dev/null and
b/src/site/antora/modules/ROOT/images/whichjar-log4j-1.2-api.png differ
diff --git a/src/site/antora/modules/ROOT/images/whichjar-log4j-api.png
b/src/site/antora/modules/ROOT/images/whichjar-log4j-api.png
new file mode 100644
index 0000000000..194196aad3
Binary files /dev/null and
b/src/site/antora/modules/ROOT/images/whichjar-log4j-api.png differ
diff --git a/src/site/antora/modules/ROOT/pages/faq.adoc
b/src/site/antora/modules/ROOT/pages/faq.adoc
index a1b3fef318..9e5ee833b2 100644
--- a/src/site/antora/modules/ROOT/pages/faq.adoc
+++ b/src/site/antora/modules/ROOT/pages/faq.adoc
@@ -37,7 +37,7 @@ You can also specify the full path of the configuration file
using a system prop
That property can also be included in a classpath resource file named
`log4j2.component.properties`.
Web applications can specify the Log4j configuration file location with a
servlet context parameter.
-See xref:manual/webapp.adoc#ContextParams[the related page on web
applications].
+See {logging-services-url}/log4j/jakarta[the Log4j Jakarta project] for
details.
Refer to xref:manual/configuration.adoc[the Configuration page] for further
details.
@@ -65,7 +65,7 @@ Configurator.reconfigure(configSourceUri);
Normally there is no need to do this manually.
Each `LoggerContext` registers a shutdown hook that takes care of releasing
resources when the JVM exits, unless the `log4j.shutdownHookEnabled` system
property is set to `false`.
-Likewise, xref:manual/webapp.adoc[Web applications] replace the shutdown hook
with their own resource management mechanisms.
+Likewise, {logging-services-url}/log4j/jakarta[Web applications] replace the
shutdown hook with their own resource management mechanisms.
That is, they clean up necessary resources when the web application is stopped.
However, if you need to manually shut down Log4j, you can use one of the
`shutdown()` methods of
link:../javadoc/log4j-api/org/apache/logging/log4j/LogManager.html#shutdown()[`LogManager`].
diff --git a/src/site/antora/modules/ROOT/pages/log4j-mongodb4.adoc
b/src/site/antora/modules/ROOT/pages/log4j-mongodb.adoc
similarity index 100%
rename from src/site/antora/modules/ROOT/pages/log4j-mongodb4.adoc
rename to src/site/antora/modules/ROOT/pages/log4j-mongodb.adoc
