[MGNLCE-102] Manage versions of module's old GAVs in parent pom for compatibility and to simplify migrations Created: 18/Oct/17 Updated: 27/Oct/17 Resolved: 26/Oct/17 |
|
| Status: | Closed |
| Project: | Community Edition |
| 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: |
|
||||||||
| Template: |
|
||||||||
| Acceptance criteria: |
Empty
|
||||||||
| Task DoR: |
Empty
|
||||||||
| Epic Link: | Remove Content API | ||||||||
| Sprint: | Basel 119 | ||||||||
| Story Points: | 1 | ||||||||
| 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
|