Uploaded image for project: 'Community Edition'
  1. Community Edition
  2. MGNLCE-102

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

    XMLWordPrintable

    Details

    • Type: Task
    • Status: Closed
    • Priority: Neutral
    • Resolution: Fixed
    • Affects Version/s: None
    • Fix Version/s: 5.6
    • Component/s: None
    • Labels:
      None

      Description

      With the Content API removal effort a lot of modules received new groupIds and artifactId. Old code was moved to compatibility modules. The old GAVs are (in most cases) relocated to those compat. modules (and a notification is shown 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.

        Attachments

          Issue Links

            Activity

              People

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

                Dates

                Created:
                Updated:
                Resolved: