<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Jens Knipper on foojay.io - Friends of OpenJDK</title><link>https://foojayio.github.io/website/today/author/jens-knipper/</link><description>Articles written by Jens Knipper on foojay.io - Friends of OpenJDK</description><generator>Hugo</generator><language>en-us</language><lastBuildDate>Mon, 19 Jan 2026 06:00:00 +0000</lastBuildDate><atom:link href="https://foojayio.github.io/website/today/author/jens-knipper/index.xml" rel="self" type="application/rss+xml"/><item><title>foojay – Documentation as Code with AsciiDoctor, GitLab CI, and GitLab Pages</title><link>https://foojayio.github.io/website/today/documentation-as-code-with-asciidoctor-gitlab-ci-and-gitlab-pages/</link><pubDate>Mon, 19 Jan 2026 06:00:00 +0000</pubDate><guid>https://foojayio.github.io/website/today/documentation-as-code-with-asciidoctor-gitlab-ci-and-gitlab-pages/</guid><description>&lt;p&gt;Writing documentation should be as low-key as possible to remove the pain from the process. One way to achieve this is through Documentation as Code. Setting it up and configuring it may take some time, but once it&amp;rsquo;s done, you can focus on creating the content itself.&lt;/p&gt;
&lt;p&gt;As a developer, I appreciate good documentation, but writing it myself is often cumbersome and feels unrewarding &amp;mdash; especially when no one reads or uses it. The reason: documentation spread across multiple tools, with no clear way to find it.&lt;/p&gt;</description></item><item><title>Foojay Podcast #73: JCon Report, Part 2 – Evolutions in the Java language and runtime</title><link>https://foojayio.github.io/website/today/foojay-podcast-73/</link><pubDate>Mon, 16 Jun 2025 07:42:00 +0000</pubDate><guid>https://foojayio.github.io/website/today/foojay-podcast-73/</guid><description>&lt;p&gt;In the second part of our JCON interviews, recorded at the conference in May, we focuses on general evolutions within the Java world and how they influence how we write code and develop applications. We take a look back at the history of Java, discuss new features in the latest release, how Java evolves with OpenJDK projects and JEPS, how Java is used in education, and much more&amp;hellip;&lt;/p&gt;
&lt;h2 id="h2-0-video"&gt;Video&lt;/h2&gt;
&lt;div style="position: relative; padding-bottom: 56.25%; height: 0; overflow: hidden;"&gt;
			&lt;iframe allow="accelerometer; autoplay; clipboard-write; encrypted-media; gyroscope; picture-in-picture; web-share; fullscreen" loading="eager" referrerpolicy="strict-origin-when-cross-origin" src="https://www.youtube.com/embed/T9_5LYsFZn8?autoplay=0&amp;amp;controls=1&amp;amp;end=0&amp;amp;loop=0&amp;amp;mute=0&amp;amp;start=0" style="position: absolute; top: 0; left: 0; width: 100%; height: 100%; border:0;" title="YouTube video"&gt;&lt;/iframe&gt;
		&lt;/div&gt;

&lt;h2 id="h2-1-podcast-apps"&gt;Podcast Apps&lt;/h2&gt;
&lt;p&gt;You can listen and subscribe to the Foojay Podcast on:&lt;/p&gt;</description></item><item><title>Receiving mails in Java with IMAP or POP3</title><link>https://foojayio.github.io/website/today/receiving-mails-in-java-with-imap-or-pop3/</link><pubDate>Fri, 24 Jan 2025 10:33:44 +0000</pubDate><guid>https://foojayio.github.io/website/today/receiving-mails-in-java-with-imap-or-pop3/</guid><description>&lt;p&gt;&lt;strong&gt;I was recently in need to write some small demo project which was receiving and processing mails. There is a lot of documentation for sending mails, but gathering information about the receiving and processing part is less easy.&lt;/strong&gt;&lt;/p&gt;
&lt;p&gt;This example shows you how to receive mails in Java either using the IMAP or the POP3 protocol. The SSL encrypted variants IMAPS and POP3S are also supported. Received mails will be set to read, which means that you will only receive the latest ones. I will also give some hints about how to handle incoming mails concerning application security. Remember that you should always sanitize user inputs.&lt;/p&gt;</description></item></channel></rss>