This is an automated email from the ASF dual-hosted git repository.

rpopma pushed a commit to branch asf-staging
in repository https://gitbox.apache.org/repos/asf/logging-log4j-site.git


The following commit(s) were added to refs/heads/asf-staging by this push:
     new 6caea77  Add images to migration page
6caea77 is described below

commit 6caea774eccc15a944bd9fb7cc5ef55e05aa61ae
Author: Remko Popma <rem...@yahoo.com>
AuthorDate: Sat Dec 25 13:04:38 2021 +0900

    Add images to migration page
---
 log4j-2.17.0/images/whichjar-log4j-1.2-api.png | Bin 0 -> 24992 bytes
 log4j-2.17.0/images/whichjar-log4j-api.png     | Bin 0 -> 16515 bytes
 log4j-2.17.0/manual/migration.html             |  11 +++++++----
 3 files changed, 7 insertions(+), 4 deletions(-)

diff --git a/log4j-2.17.0/images/whichjar-log4j-1.2-api.png 
b/log4j-2.17.0/images/whichjar-log4j-1.2-api.png
new file mode 100644
index 0000000..8b54810
Binary files /dev/null and b/log4j-2.17.0/images/whichjar-log4j-1.2-api.png 
differ
diff --git a/log4j-2.17.0/images/whichjar-log4j-api.png 
b/log4j-2.17.0/images/whichjar-log4j-api.png
new file mode 100644
index 0000000..194196a
Binary files /dev/null and b/log4j-2.17.0/images/whichjar-log4j-api.png differ
diff --git a/log4j-2.17.0/manual/migration.html 
b/log4j-2.17.0/manual/migration.html
index 7b62356..376a9d5 100644
--- a/log4j-2.17.0/manual/migration.html
+++ b/log4j-2.17.0/manual/migration.html
@@ -182,6 +182,8 @@
                           the Log4j 1.x bridge jar (log4j-1.2-api.jar).
                       </p>
 
+                      <p><img src="../images/whichjar-log4j-1.2-api.png" 
alt="Using log4j 2 via the log4j 1.x API" /></p>
+
                       <p>
                           For most applications this is sufficient.
                           This is a low-effort way to migrate, and may also 
allow for migration to proceed gradually over time.
@@ -235,13 +237,12 @@
                   <section>
                       <h3><a 
name="Option_2:_convert_your_application_to_the_Log4j_2_API_.28log4j-api.29"></a>Option
 2: convert your application to the Log4j 2 API (log4j-api)</h3>
 
-                      <p>
-                          The other migration option involves changing your 
application code to use
-                          the Log4j 2 API.
-                          For the most part, converting from the Log4j 1.x API 
to Log4j 2 should be fairly simple. Many
+                      <p>For the most part, converting from the Log4j 1.x API 
to Log4j 2 should be fairly simple. Many
                           of the log statements will require no modification. 
However, where necessary the following changes must be
                           made.</p>
 
+                      <p><img src="../images/whichjar-log4j-api.png" 
alt="Using log4j 2 via the log4j 2.x API" /></p>
+
                       <table border="0" class="table table-striped" 
width="100%">
 
                           <tr class="a">
@@ -343,6 +344,8 @@
                       <h3><a 
name="Migrating_logging_configurations_to_the_Log4j_2_format"></a>Migrating 
logging configurations to the Log4j 2 format</h3>
 
                       <p>
+                          The other migration option involves changing your 
application code to use
+                          the Log4j 2 API.
                           Although the Log4j 2 configuration syntax is 
different than that of Log4j 1.x, most, if not all, of
                           the same functionality is available.
                       </p>

Reply via email to