Port system properties documentation to main

Part of #2525

Author: ppkarwasz

log4j-async-logger/pom.xml

@@ -31,6 +31,8 @@
   <description>Alternative implementation of logger that uses LMAX Disruptor.</description>
 
   <properties>
+    <maven.javadoc.skip>false</maven.javadoc.skip>
+
     <bnd-extra-package-options>
       <!-- JSpecify is optional at runtime -->
       org.jspecify.annotations.*;resolution:=optional

src/site/antora/modules/ROOT/pages/javadoc.adoc

@@ -16,15 +16,17 @@
 ////
 = Javadoc API Documentation
 
-The table below contains links to the Javadoc API Documentation for the components you are most likely to use
-directly in code. You can also use the menu links on the left.
+The table below contains links to the Javadoc API Documentation for the components you are most likely to use directly in code.
 
 |===
 |Component |Description
 
-|link:javadoc/log4j-api[Log4j 3.x API]
+|link:/log4j/2.x/javadoc/log4j-api[Log4j 2 API]
 |The interface that applications should use and code against.
 
-|link:javadoc/log4j-core[Implementation]
-|The standard implementation, also called the Log4j 3.x Core, that contains Appenders, Filters, and more.
+|link:javadoc/log4j-core/index.html[Implementation]
+|The standard implementation, also called the Log4j 3 Core, that contains Appenders, Filters, and more.
+
+|link:javadoc/log4j-async-logger/index.html[Asynchronous logger]
+|An alternative asynchronous logger implementation for Log4j 3 Core, based on LMAX Disruptor.
 |===

src/site/antora/modules/ROOT/pages/manual/async.adoc

@@ -103,8 +103,7 @@ are not garbage-free since they
 cause `java.util.concurrent.locks.AbstractQueuedSynchronizer$Node` objects to be created.
 The default wait strategy used by Log4j uses a synchronized block instead of a ReentrantLock to avoid this problem.
 The Yield and Sleep wait strategies are garbage-free. (For configuring predefined wait strategies, see
-xref:manual/async.adoc#SysPropsAllAsync[here] and
-xref:manual/async.adoc#SysPropsMixedSync-Async[here],
+xref:manual/systemproperties.adoc#properties-log4j-async-logger[here],
 you may also configure a xref:manual/async.adoc#WaitStrategy[custom wait strategy].)
 
 === Disabling Garbage-free Logging
@@ -125,7 +124,7 @@ performance is important, consider using Async Loggers.
 Instead of system properties, the above properties can also be specified
 in a file named `log4j2.component.properties` by including this file in
 the classpath of the application. See the
-xref:manual/configuration.adoc#SystemProperties[manual regarding system
+xref:manual/systemproperties.adoc[manual regarding system
 properties] for more info.
 
 [#Appenders]
@@ -437,7 +436,7 @@ spike in service time adds queueing delay for many of the subsequent
 operations. Service time is easy to measure (and often looks good on
 paper) but is irrelevant for users since it omits the time spent waiting
 for service. For this reason we report response time: service time plus
-wait time. See the xref:manual/performance.adoc#responseTime[response time
+wait time. See the xref:manual/performance.adoc[response time
 section] of the performance page for more detail.
 
 The response time test results below were all derived from running the

src/site/antora/modules/ROOT/pages/manual/garbagefree.adoc

@@ -109,7 +109,10 @@ in each web application.
 
 The `JndiContextSelector` will not work unless `log4j2.enableJndi=true` is set as a system property
 or environment variable. See the
-xref:manual/configuration.adoc#enableJndi[log4j2.enableJndi] system property.
+xref:manual/systemproperties.adoc#log4j.jndi.enableContextSelector[log4j.jndi.enableContextSelector]
+configuration property.
+
+xref:manual/systemproperties.adoc#log4j2
 
 The exact method for setting system properties depends on the container.
 For Tomcat, edit `$CATALINA_HOME/conf/catalina.properties`. Consult the