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.