<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Build on JAVAPRO International</title><link>https://javapro-en.svenruppert.com/tags/build/</link><description>Recent content in Build on JAVAPRO International</description><generator>Hugo</generator><language>en-US</language><lastBuildDate>Tue, 26 Aug 2025 07:00:01 +0000</lastBuildDate><atom:link href="https://javapro-en.svenruppert.com/tags/build/index.xml" rel="self" type="application/rss+xml"/><item><title>How to Speed up Maven Builds</title><link>https://javapro-en.svenruppert.com/how-to-speed-up-maven-builds/</link><pubDate>Tue, 26 Aug 2025 07:00:01 +0000</pubDate><guid>https://javapro-en.svenruppert.com/how-to-speed-up-maven-builds/</guid><description>&lt;p&gt;As a Maven project grows in size, the question of build speed and test execution time becomes more important. One of the most obvious ways to optimize is to switch to another build system (e.g., Gradle). However, before making the switch (which will inevitably bring new challenges—we’ll discuss this at the end), let’s first explore what we can do to speed things up while staying on Maven. Many of these tips will be useful regardless, even if you eventually decide to migrate.&lt;/p&gt;</description></item></channel></rss>