You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@logging.apache.org by rp...@apache.org on 2021/12/30 06:21:11 UTC

[logging-log4j2] branch release-2.x updated: [DOC] minor changes

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

rpopma pushed a commit to branch release-2.x
in repository https://gitbox.apache.org/repos/asf/logging-log4j2.git


The following commit(s) were added to refs/heads/release-2.x by this push:
     new d6bb11e  [DOC] minor changes
d6bb11e is described below

commit d6bb11e29a8a2d9e8c83e4b5f5adee8b552b280b
Author: rpopma <rp...@apache.org>
AuthorDate: Thu Dec 30 15:21:03 2021 +0900

    [DOC] minor changes
---
 src/site/markdown/manual/migration.md | 2 +-
 src/site/markdown/security.md         | 4 ++--
 2 files changed, 3 insertions(+), 3 deletions(-)

diff --git a/src/site/markdown/manual/migration.md b/src/site/markdown/manual/migration.md
index 1e3a725..1b5a49f 100644
--- a/src/site/markdown/manual/migration.md
+++ b/src/site/markdown/manual/migration.md
@@ -19,7 +19,7 @@
 ## Migrating from Log4j 1.x to 2.x
 [Log4j 1.x](http://logging.apache.org/log4j/1.2/) has
 [reached End of Life](https://blogs.apache.org/foundation/entry/apache_logging_services_project_announces)
-and is no longer supported.
+in 2015 and is no longer supported.
 
 This page explains how to migrate applications or libraries currently using the Log4j 1.x API
 to use Log4j v2 as their main logging framework.
diff --git a/src/site/markdown/security.md b/src/site/markdown/security.md
index 2f59475..70b1dc1 100644
--- a/src/site/markdown/security.md
+++ b/src/site/markdown/security.md
@@ -30,9 +30,9 @@ reported against Log4j or where Log4j provides a workaround are listed at the en
 
 Please note that [Log4j 1.x](http://logging.apache.org/log4j/1.2/) has 
 [reached End of Life](https://blogs.apache.org/foundation/entry/apache_logging_services_project_announces)
-and is no longer supported.
+in 2015 and is no longer supported.
 Vulnerabilities reported after August 2015 against Log4j 1.x were not checked and will not be fixed.
-Users should upgrade to Log4j 2 to obtain security fixes.
+Users should [upgrade to Log4j 2](manual/migration.html) to obtain security fixes.
 
 Please note that binary patches are never provided. If you need to apply a source code patch,
 use the building instructions for the Apache Log4j version that you are using.