[BUILD-1179] Introduce a safety net step that makes sure there is no leftover SNAPSHOT after automatic dependency resolution Created: 30/Oct/23  Updated: 02/Nov/23  Resolved: 02/Nov/23

Status: Closed
Project: Build
Component/s: None
Affects Version/s: None
Fix Version/s: None

Type: Task Priority: Neutral
Reporter: Maxime Michel Assignee: Maxime Michel
Resolution: Done Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
relation
is related to MGNLEE-815 We shouldn't have to release two cont... Open
Template:
Acceptance criteria:
Empty
Task DoR:
Empty
Work Started:

 Description   

In release-job. This would make sure that we never ever mistakingly ship a release that includes a SNAPSHOT dep, such as what happened with 6.2.40.

Unlike the automatic resolution of versions which happens exclusively in the root pom, this should also scan for such issues in submodule, such as what happened here: https://git.magnolia-cms.com/projects/ENTERPRISE/repos/content-editor/commits/cc67a866673531c33953be005118a85aae3eaf2b#test/pom.xml?f=17


Generated at Sun Feb 11 23:48:53 CET 2024 using Jira 9.4.2#940002-sha1:46d1a51de284217efdcb32434eab47a99af2938b.