[MGNLMIGRATION-319] Migration project could depend on lower versions Created: 25/Apr/14 Updated: 29/Apr/14 Resolved: 29/Apr/14 |
|
| Status: | Closed |
| Project: | Migration 4.4 to 4.5 (closed) |
| Component/s: | None |
| Affects Version/s: | 1.2.8 |
| Fix Version/s: | 1.2.9 |
| Type: | Bug | Priority: | Neutral |
| Reporter: | Roman Kovařík | Assignee: | Robert Šiška |
| Resolution: | Fixed | Votes: | 0 |
| Labels: | maintenance | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Attachments: |
|
||||||||||||||||
| Issue Links: |
|
||||||||||||||||
| Template: |
|
||||||||||||||||
| Acceptance criteria: |
Empty
|
||||||||||||||||
| Date of First Response: | |||||||||||||||||
| Description |
|
We set module versions to latest snapshots when adding integration tests to Migration project (see |
| Comments |
| Comment by Milan Divilek [ 28/Apr/14 ] |
|
Reopen: Migration module has to stay in maintenance mode, because dependency to magnolia main was downgraded only to 4.5.13 which is in maintenance mode. If we want remove maintenance mode from Migration module then we need downgrade dependency to magnolia main at least to version 4.5.12. In magnolia-migration-tests/pom.xml can you add property with magnolia main version and then use this property instead of having version number everywhere. |
| Comment by Eric Hechinger [ 29/Apr/14 ] |
|
un-necessary revert |