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 d49b47e Fix copy-paste error in migration page
d49b47e is described below
commit d49b47e68abdc073368740ebd47913b52992c5d4
Author: Remko Popma <rem...@yahoo.com>
AuthorDate: Sat Dec 25 13:07:50 2021 +0900
Fix copy-paste error in migration page
---
log4j-2.17.0/manual/migration.html | 8 +++++---
1 file changed, 5 insertions(+), 3 deletions(-)
diff --git a/log4j-2.17.0/manual/migration.html
b/log4j-2.17.0/manual/migration.html
index 376a9d5..a3194a0 100644
--- a/log4j-2.17.0/manual/migration.html
+++ b/log4j-2.17.0/manual/migration.html
@@ -237,7 +237,10 @@
<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>For the most part, converting from the Log4j 1.x API
to Log4j 2 should be fairly simple. Many
+ <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
of the log statements will require no modification.
However, where necessary the following changes must be
made.</p>
@@ -344,8 +347,6 @@
<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>
@@ -644,6 +645,7 @@
</main>
+
</div>
</div>
<hr/>
