[MGNLEE-509] Manage versions of module's old GAVs in parent pom for compatibility and to simplify migrations Created: 18/Oct/17  Updated: 06/Nov/17  Resolved: 03/Nov/17

Status: Closed
Project: Magnolia DX Core
Component/s: None
Affects Version/s: None
Fix Version/s: 5.6

Type: Task Priority: Neutral
Reporter: Philip Mundt Assignee: Federico Grilli
Resolution: Fixed Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Relates
relates to MGNLCE-102 Manage versions of module's old GAVs ... Closed
Template:
Acceptance criteria:
Empty
Task DoR:
Empty
Epic Link: Remove Content API
Sprint: Basel 119, Basel 120, Basel 121
Story Points: 1

 Description   

With the Content API removal effort a lot of modules received new groupIds and artifactId. Old code was move to compatibility modules. The old GAVs are (in most cases) relocated to those compat. modules (and a notification is show if the old GAV is still used). As some clients might be relying on those versions set in the parent pom (via dependency management import), we should maintain them in the parent poms

  • to ease the migration to the new GAVs and
  • so that the relocation works and a message is shown.

Todo:

  • Add old GAV to (group of) new dependencies
  • Add a pom property if applicable
  • Add comment that the dep is added for compat. only.

Generated at Mon Feb 12 05:30:42 CET 2024 using Jira 9.4.2#940002-sha1:46d1a51de284217efdcb32434eab47a99af2938b.