[MAGNOLIA-5187] Define dependency on migration module in bundles Created: 16/Jul/13 Updated: 26/Jul/13 Resolved: 23/Jul/13 |
|
| Status: | Closed |
| Project: | Magnolia |
| Component/s: | None |
| Affects Version/s: | None |
| Fix Version/s: | 4.5.10, 5.0.2, 5.1 |
| Type: | Improvement | Priority: | Neutral |
| Reporter: | Milan Divilek | Assignee: | Milan Divilek |
| 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 DoD: |
[ ]*
Doc/release notes changes? Comment present?
[ ]*
Downstream builds green?
[ ]*
Solution information and context easily available?
[ ]*
Tests
[ ]*
FixVersion filled and not yet released
[ ] 
Architecture Decision Record (ADR)
|
||||||||
| Date of First Response: | |||||||||
| Description |
|
Right now DMS module (categorization at 5.x) brings migration module into bundle because dependency scope is compile. When we need deploy new version of migration module into bundle we have to update migration version in DMS module. We should add dependency to migration into bundle. |
| Comments |
| Comment by Magnolia International [ 19/Jul/13 ] |
|
Needs merge in 5.0.x branch |