This is an automated email from the ASF dual-hosted git repository.
git-site-role pushed a commit to branch asf-staging
in repository https://gitbox.apache.org/repos/asf/logging-site.git
The following commit(s) were added to refs/heads/asf-staging by this push:
new d606a627 Automatic Site Publish by Buildbot
d606a627 is described below
commit d606a6270423fbd9cea26541fd0543b4976ea100
Author: buildbot <[email protected]>
AuthorDate: Fri Apr 19 15:52:47 2024 +0000
Automatic Site Publish by Buildbot
---
content/blog/2023/12/02/apache-common-logging-1.3.0.html | 4 ++--
content/feed.xml | 6 +++---
2 files changed, 5 insertions(+), 5 deletions(-)
diff --git a/content/blog/2023/12/02/apache-common-logging-1.3.0.html
b/content/blog/2023/12/02/apache-common-logging-1.3.0.html
index 3e2bdfcc..da0a04c5 100644
--- a/content/blog/2023/12/02/apache-common-logging-1.3.0.html
+++ b/content/blog/2023/12/02/apache-common-logging-1.3.0.html
@@ -121,8 +121,8 @@ In Maven this can be done using dependency management.</p>
</code></pre></div></div>
<p>The second step consists in removing obsolete dependencies.
-Since version 1.2 only supported old generation logging backends
out-of-the-box (<a href="https//logging.apache.org/log4j/1.2/">Log4j 1.x</a>,
-<a href="https//avalon.apache.org">Avalon</a> and <a
href="https://javalogging.sourceforge.net";>Lumberjack</a>), the Java community
developed
+Since version 1.2 only supported old generation logging backends
out-of-the-box (<a href="https://logging.apache.org/log4j/1.x/";>Log4j 1.x</a>,
+<a href="https://avalon.apache.org";>Avalon</a> and <a
href="https://javalogging.sourceforge.net";>Lumberjack</a>), the Java community
developed
many <code class="language-plaintext highlighter-rouge">LogFactory</code>
implementations and complete Apache Commons Logging replacements:</p>
<ul>
diff --git a/content/feed.xml b/content/feed.xml
index 295449b5..21d19142 100644
--- a/content/feed.xml
+++ b/content/feed.xml
@@ -1,4 +1,4 @@
-<?xml version="1.0" encoding="utf-8"?><feed
xmlns="http://www.w3.org/2005/Atom"; ><generator uri="https://jekyllrb.com/";
version="4.2.2">Jekyll</generator><link href="/feed.xml" rel="self"
type="application/atom+xml" /><link href="/" rel="alternate" type="text/html"
/><updated>2024-04-19T07:57:57+00:00</updated><id>/feed.xml</id><title
type="html">Apache Software Foundation - Logging
Services</title><subtitle>Write an awesome description for your new site here.
You can edit this line in _ [...]
+<?xml version="1.0" encoding="utf-8"?><feed
xmlns="http://www.w3.org/2005/Atom"; ><generator uri="https://jekyllrb.com/";
version="4.2.2">Jekyll</generator><link href="/feed.xml" rel="self"
type="application/atom+xml" /><link href="/" rel="alternate" type="text/html"
/><updated>2024-04-19T15:52:46+00:00</updated><id>/feed.xml</id><title
type="html">Apache Software Foundation - Logging
Services</title><subtitle>Write an awesome description for your new site here.
You can edit this line in _ [...]
<p>Today, December 17, 2023 marks a significant milestone for the Apache
Logging Services project,
as we celebrate 20 years since the inception of Log4j 1.
@@ -133,8 +133,8 @@ In Maven this can be done using dependency management.</p>
</code></pre></div></div>
<p>The second step consists in removing obsolete dependencies.
-Since version 1.2 only supported old generation logging backends
out-of-the-box (<a href="https//logging.apache.org/log4j/1.2/">Log4j 1.x</a>,
-<a href="https//avalon.apache.org">Avalon</a> and <a
href="https://javalogging.sourceforge.net";>Lumberjack</a>), the Java community
developed
+Since version 1.2 only supported old generation logging backends
out-of-the-box (<a href="https://logging.apache.org/log4j/1.x/";>Log4j 1.x</a>,
+<a href="https://avalon.apache.org";>Avalon</a> and <a
href="https://javalogging.sourceforge.net";>Lumberjack</a>), the Java community
developed
many <code class="language-plaintext highlighter-rouge">LogFactory</code>
implementations and complete Apache Commons Logging replacements:</p>
<ul>
