[MBUILDCACHE-77] Archetypes can't be build using maven build cache in CI/CD environments.

• Type: Bug
• Status: Open
• Priority: Major
• Resolution: Unresolved
• Affects Version/s: 1.1.0
• Component/s: remote build cache
• Assignee: Unassigned
• Reporter: aitor moragas
• Created: 14/Dec/23 10:03
• Updated: 14/Dec/23 10:12

Description

Our build  in the CI/CD pipeline is like follows:

 

• compute next version
• update next version in all components
• launch build

 

For archetype projects the build can never be cached because of the way the hash is computed.

This is a snippet of the buildinfo.xml file produced:

 

 

  </project>
    </item>
      <!-- other items -->
      <item type="file" hash="c5021fd9037b1aca" isText="unknown" charset="US-ASCII" eol="LF">../../pom.xml</item>
    </items>
  </projectsInputInfo>
</build> 

The fact that the parent pom.xml has been updated with the new version makes it impossible that the hash matches and therefore the build is always done (never skipped as present in the cache).

 

When computing the effective pom, we need something equivalent to <excludedproperty> for maven plugins.