Uploaded image for project: 'Magnolia DX Core'
  1. Magnolia DX Core
  2. MGNLEE-509

Manage versions of module's old GAVs in parent pom for compatibility and to simplify migrations

    XMLWordPrintable

Details

    • Task
    • Resolution: Fixed
    • Neutral
    • 5.6
    • None
    • None
    • None
    • Basel 119, Basel 120, Basel 121
    • 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.

      Checklists

        Acceptance criteria

        Attachments

          Issue Links

            Activity

              People

                fgrilli Federico Grilli
                pmundt Philip Mundt
                Votes:
                0 Vote for this issue
                Watchers:
                2 Start watching this issue

                Dates

                  Created:
                  Updated:
                  Resolved:

                  Checklists

                    Task DoR