<?xml version="1.0" encoding="utf-8" standalone="yes"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
  <channel>
    <title>Maven - Tag - Techland</title>
    <link>https://techland.info/en/tags/maven/</link>
    <description>Blog dédié à la tech en général</description>
    <generator>Hugo 0.165.0 &amp; FixIt v1.0.0-alpha.3</generator>
    <language>en</language>
    <managingEditor>contact@techland.info (LE BARO Romain)</managingEditor>
    <webMaster>contact@techland.info (LE BARO Romain)</webMaster>
    <lastBuildDate>Mon, 05 Oct 2026 21:19:28 +0200</lastBuildDate>
    <atom:link href="https://techland.info/en/tags/maven/index.xml" rel="self" type="application/rss+xml" /><item>
      <title>Maven: One Phase per CI Stage</title>
      <link>https://techland.info/en/posts/java/maven-one-phase-by-ci-stage/</link>
      <pubDate>Mon, 05 Oct 2026 21:19:28 +0200</pubDate><author>contact@techland.info (LE BARO Romain)</author>
      <guid>https://techland.info/en/posts/java/maven-one-phase-by-ci-stage/</guid>
      <category domain="https://techland.info/en/categories/development/">Development</category>
      <description>&lt;p&gt;Have you ever tried running Maven phases in different stages/jobs of a CI pipeline? If so, you have probably run into an annoying issue where Maven re-runs the phases already executed in previous jobs, even though the files produced by the previous phase are present. Let&amp;rsquo;s see how to fix that!&lt;/p&gt;</description>
    </item>
  </channel>
</rss>
