<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Logging on JAVAPRO International</title><link>https://javapro-en.svenruppert.com/tags/logging/</link><description>Recent content in Logging on JAVAPRO International</description><generator>Hugo</generator><language>en-US</language><lastBuildDate>Tue, 10 Jun 2025 07:00:01 +0000</lastBuildDate><atom:link href="https://javapro-en.svenruppert.com/tags/logging/index.xml" rel="self" type="application/rss+xml"/><item><title>The long history of log4j</title><link>https://javapro-en.svenruppert.com/the-long-history-of-log4j/</link><pubDate>Tue, 10 Jun 2025 07:00:01 +0000</pubDate><guid>https://javapro-en.svenruppert.com/the-long-history-of-log4j/</guid><description>&lt;p&gt;Logging is the art of making sense of a system.&lt;/p&gt;
&lt;p&gt;Software writes lines of information into log files, and developers sift through them, hoping to find what they need. The problem? Systems rarely log the right things. Yet without those files, we&amp;rsquo;d be flying blind, unaware that anything even went wrong.&lt;/p&gt;
&lt;p&gt;This is the story of Apache Log4j—one of the oldest pieces of Java code still in use today. A tool that gave developers a way to listen to their systems.&lt;/p&gt;</description></item></channel></rss>